> 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). On Mon, Apr 20, 2020 at 4:20 PM Gregory Nutt <spudan...@gmail.com> wrote: > > > > But how we describe 9.0 release? Most people will ask two questiones: > > 1.When(or commit id) the release branch out from master > We know this from the branch creation > > 2.Which patch we cherry-pick from master after the branch is created > This we can get from the pose branch PRs > > and then the huge cherry-pick list just confuse the people why so many > > minor change enter into the release branch. > > 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. >
