Hi Folks, just a suggestion ... if you want to start a release ... I would suggest to do one of these two:
- Announce that a release candidate will be created in a week or so and to ask everyone to do an audit of the codebase prior tot hat - Cut a release-branch and announce a code-freeze phase of a week or so on that branch and ask everyone to do an audit of the codebase there ... in this code-freeze phase only fixes to release-relevant things should be allowed (No new features or regular development) (I would opt for option 2 - release branch with code stabilization phase) Reasoning behind this: At least I will be doing some thorough checks on the release ... especially for the first releases, the chance is high, that there will be problems and this could cause a lot of release candidates. If we spot things early, this is a lot less work for the Release Manager. So if you want to avoid doing too many extra loops, do your checks first and produce the official release artifact after a stabilization phase. Chris -----Ursprüngliche Nachricht----- Von: Alexander Alten <[email protected]> Gesendet: Dienstag, 10. August 2021 08:48 An: [email protected] Betreff: release Hey dev community, I’d suggest we start to draft our first release, I know we might miss something in the documentation, but I also believe the docs are a living space. Means we can update them more agile. What do you think? Cheers, —Alex — PPMC Apache Wayang [email protected]
