-
-
Notifications
You must be signed in to change notification settings - Fork 26
Release process
George Hicken edited this page Mar 14, 2024
·
6 revisions
Check list for new release tagging:
- Create release branch
- Copy current sheet to new WIP
- Sanitize current sheet to be tagged
- Rename current sheet to version with focus indication
- Add to-be release number and link to cell in Summary
- Add sheet to release branch
- Export sheet to human readable and add to branch
- Export AppScript files and add to branch
- Review branch and fix up any sheet errors
- Repeat until no changes
- Export xlsx version of the sheet
- Rename xlsx to
VMW_to_AVGO_ESPP_and_RSU.xlsx
- Create Excel compatible version
- Upload Excel compatible version to OneDrive and share
- Update README release status section with the new release
- Update both G-suite and Office links
- This has an embedded link to the shared sheet in the Getting Started step 3
- Update Install with any changes
- Merge the branch
- Create a new release
- Add link to the specific shared sheet version in the Release description
- G-suite
- Office365
- Rename xlsx version to
VMW_to_AVGO_ESPP_and_RSU-v0.0.0-github.xlsx
adjusting version appropriately - Add xlsx as Asset to the release
- Add a
- for excel
variant to the release - Ensure fixed issues and PRs are associated with the release (track down specifics as to what this needs)
- Check the
pre-release
box - Release
- Update
latest
tag
- Add link to the specific shared sheet version in the Release description
- Update old shared sheets with link to latest and date of change.
- Create branch for next release if not already present and switch to it