Release procedure - Githubissues

zowe / community

Zowe Community - Sub-projects, Squads, Contribution Guidelines, Meeting Minutes, and more

53 stars 42 forks source link

Release procedure #1862

Open balhar-jakub opened 1 year ago

balhar-jakub commented 1 year ago

The current release procedure seems to be complex and again starts delaying the release. On top of that in order to release we are breaking the rules on the protected branches, which is something we should also limit.

What can we do to improve the situation?

1) Update the way we release snapshots and when releasing just agree on a snapshot to release . 2) ...

Thank you for taking the time to submit a topic for the architecture call. diff --git a/.github/ISSUE_TEMPLATE/tsc_requests.md b/.github/ISSUE_TEMPLATE/tsc_requests.md

balhar-jakub commented 1 year ago

Action Items: 1) All squads verify their components in Nightly are in the correct version

API ML
Jobs
Datasets
ZSS
Launcher
zwe
Config Manager 2) We explore the option to rollback to the last working nightly build as the RC and release within the next PI.

balhar-jakub commented 1 year ago

We will return to doing the retrospectives on the release to learn from our problems.

boris-bc commented 1 year ago

For me a problem with Zowe Releases is the difficulty to identify whether an issue is planned for or has made it into a release. ZenHub seems to have support for release planning, not sure if it could be leveraged. https://help.zenhub.com/support/solutions/articles/43000010359-plan-long-term-projects-with-release-reports

balhar-jakub commented 1 year ago

@boris-bc I created a separate issue for the request - https://github.com/zowe/community/issues/1963 And transformed this issue into Epic as there are more topics around release to handle.