|[mdt-papyrus.dev] Papyrus Photon - Release preparation|
This mail mainly concerns the committers but can be a useful reminder for everyone else too ;)
As the release approaches, the Master branch should only receive approved bug fixes on existing problems. Any new features should be committed in their own branches (prefer the format: bugs/**** as this can be easily removed by any committer) and merged after the official release (June 27). New jobs can be created for these branches in order to test them if need be.
This is to keep a ‘clean’ branch in case any new build is needed, tag the release, and have enough time to see if the integration happens smoothly over the quiet week.
Cheers and Thanks,
The Papyrus team
Back to the top