...
To: dev@fineract.apache.org Subject: Re: Fineract $RELEASE release branch
As previously announced, I've just created the release branch for our upcoming $RELEASE release.
You can continue working and merging PRs to the develop branch for future releases, as always.
The DRAFT release notes are on https://cwiki.apache.org/confluence/display/FINERACT/$RELEASE+-+Apache+Fineract. Does anyone see anything missing?
Does anyone have any last minutes changes they would like to see cherry-picked to branch $RELEASE, or are we good go and actually cut the release based on this branch as it is?
I'll initial the final stage of actually creating the release in 3 days if nobody objects.
Thanks, $RM |
With the release branch we draw a line in the side, but development on the develop branch will usually continue after the release branch is created. If changes on develop need to be included in the still open release branch then do so by cherry picking selectively.
Cherry picking should only happen from the develop branch, i. e. do not pick changes from PRs that are not yet merged. That way we ensure that we don't pick up anything too experimental or just plain not working.
5. Freeze JIRA, create release tag, build distribution, digitally sign it, upload it, call for PMC vote
...