NOTICE:
Branch release-0.6 has been cut and version references on 'main' have been updated to v0.7.0-prerelease. I intend to proceed with an RC in relatively short order, since no one mentioned having work outstanding for the release in the "Operator 0.6.0 Release" thread, and all the tickets on the Github "milestone" are already closed. However, in the interim, please remember to observe the normal rules: * No new features may be committed to release-0.6. * Documentation patches, build patches and serious bug fixes may be committed to release-0.6. However, you should submit all issues/PRs you want to commit to Github first to give others the chance to review and possibly vote against the PR. Keep in mind that it is our main intention to keep the branch as stable as possible. * All patches that are intended for release-0.6 should first be committed to the unstable branch, merged into the stable branch, and then into the current release branch. * Normal unstable and stable branch development may continue as usual. However, if you plan to commit a big change to the unstable branch while the branch feature freeze is in effect, think twice: can't the addition wait a couple more days? Merges of bug fixes into the branch may become more difficult. * Only Github issues with Milestone v0.6.0 and priority "Blocker" will delay a release candidate build. Best, Jason --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
