Skip to content

Release process

George Hicken edited this page Mar 14, 2024 · 6 revisions

Check list for new release tagging:

  1. Create release branch
  2. Copy current sheet to new WIP
  3. Sanitize current sheet to be tagged
  4. Rename current sheet to version with focus indication
  5. Add to-be release number and link to cell in Summary
  6. Add sheet to release branch
    1. Export sheet to human readable and add to branch
    2. Export AppScript files and add to branch
    3. Review branch and fix up any sheet errors
    4. Repeat until no changes
    5. Export xlsx version of the sheet
    6. Rename xlsx to VMW_to_AVGO_ESPP_and_RSU.xlsx
  7. Create Excel compatible version
    1. Upload Excel compatible version to OneDrive and share
  8. Update README release status section with the new release
    1. Update both G-suite and Office links
    2. This has an embedded link to the shared sheet in the Getting Started step 3
  9. Update Install with any changes
  10. Merge the branch
  11. Create a new release
    1. Add link to the specific shared sheet version in the Release description
      1. G-suite
      2. Office365
    2. Rename xlsx version to VMW_to_AVGO_ESPP_and_RSU-v0.0.0-github.xlsx adjusting version appropriately
    3. Add xlsx as Asset to the release
    4. Add a - for excel variant to the release
    5. Ensure fixed issues and PRs are associated with the release (track down specifics as to what this needs)
    6. Check the pre-release box
    7. Release
    8. Update latest tag
  12. Update old shared sheets with link to latest and date of change.
  13. Create branch for next release if not already present and switch to it
Clone this wiki locally