Hi all,
After each release we do an informal retrospective of things
that could've gone better. For pcp-3.10.4 we're planning to
make the following tweaks to the process:
- Introducing a full week of QA focus prior to the release
Feature work will not be merged in the week (7 days) leading
up to a release. We'll continue to note the expected release
dates in the changelog files for reference. We'd like to see
not just a hold on your pull requests for that week, but also
active engagement in quality assurance work if you can. Test
and documentation updates that don't risk destabilising the
build or other peoples QA work is fine at any time.
- Extending the release interval a little
Partially to cater for the above, and also allowing more time
for the QA farm(er)s to keep up with development, we're going
to switch to a 6 week release cycle instead of once a month.
- Removing the git dev/master branch distinction
Having separate dev and master branches is not proving useful
to anyone that we know of. We're planning to switch to only a
"master" branch, and dropping "dev" entirely. Release tags
will still be made for each release. A separate note will be
sent just prior to cutting over, so everyone can update their
.git/config files, etc.
Please let us know if any of these changes would inconvenience
you in any way, and lets discuss.
cheers.
--
Nathan
|