Open aaronreed708 opened 10 months ago
From @maoo: "I'd suggest to look at Github features that automatically generate Release notes, see https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes. Note that Github Actions can be triggered by new releases, which would allow you to use the Github UI to trigger the release process, and Github actions to build and publish artifacts"
The release process needs to include manual Docker scanning for now, as well as linking the manual scan results with the release somehow (more background information here: https://github.com/finos/a11y-theme-builder/issues/742)
I'll be looking into #721 as part of this and will explore @maoo 's suggestion for automatic release notes from GitHub), and @codyzu 's suggestion for beachball. Both are integrated with GitHub - will put notes here as I create examples from both and we can decide which way we'd like to go.
Problem/Concern
We need to come up with what it means to "release" Theme Builder and the SDK. There needs to be an exit criteria and a series of post-release steps that must be completed. The purpose of this issue is to define both.
Proposed Solution
Here is a list with which to start defining the exit criteria. These are just some suggestions to serve as a starting point:
Here is a list with which to start defining the exit criteria. These are just some suggestions to serve as a starting point: