community icon indicating copy to clipboard operation
community copied to clipboard

Published 20 hours ago • verified publisher icon zowe

Release procedure

Open balhar-jakub opened this issue 1 year ago • 4 comments

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 avatar Mar 16 '23 08:03 balhar-jakub

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 avatar Mar 21 '23 14:03 balhar-jakub

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

balhar-jakub avatar Mar 21 '23 14:03 balhar-jakub

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

boris-bc avatar Mar 22 '23 14:03 boris-bc

@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.

balhar-jakub avatar May 07 '23 19:05 balhar-jakub