On Thu, Dec 12, 2019 at 10:05 PM Gregory Nutt <spudan...@gmail.com> wrote: > Some of these things are difficult to discuss at this point in time > because we not have enough Apache knowledge and experience. What I have > seen from following the release emails is the release will go through > several release candidates before before a final release is made. > Tagging releases as NuttX did in the past won't support that. I believe > that you would have to use branches to support a series of release > candidates until the release is made (and perhaps even to support > further releases on the branch for bug fixes).
I think we should use release branches, unless we want to lock down the repo against all changes for the duration of the release prep -> release candidate -> testing -> debating -> voting cycle, which could take a non trivial amount of time. With a release branch, normal development can continue to be merged to master during this time. Any release-blocking bugs found during release testing get fixed on master and then merged (just those commits) to the release branch.
