On Mon, Apr 20, 2020 at 1:05 PM Gregory Nutt <spudan...@gmail.com> wrote: > >> I agree that we should not let trivial cosmetic things onto the release > >> branch. We should only permit showstopping, critical bugfixes onto the > >> release branch. It is probably a fair comment that we brought too much > >> unimportant stuff in and the confuses things. Let's add that to the > >> TIL: Only showstopping, critical bugfixes my come into the release > >> branch. Once the release branch is cut, it is not changed for any > >> reason other than to correct user-exposure to bugs. > > I don't know how unimportant are the things that got back-ported. > > There are 10 commits back-ported in nuttx/. 3 of them deal with bugs > > in macOS build. 3 are pure typos, 1 is a typo that broke the cxd56xx > > build if certain files were chosen, 1 updated the TODO file (some > > lines about a bug were outdated/incorrect), and last 2 were for tools > > and release notes (both needed by the final release). > > > I don't know how important the macOS changes are, but most if not all of > the others were certainly not show-stopping, critical bugs. The > stability and clarity of the release would probably be more important.
For future 2-month releases, I think that on the branch date, we should branch and immediately make -rc1 tarballs. Then the community can test, report bugs/showstoppers, and those will be fixed on master and backported to the branch. When it seems there are no more showstoppers, make -rc2 tarballs, let test a few more days. If no showstoppers this time, re-brand it as the final release. Nathan
