Hello Greg and all, >I think we should create a release branch and freeze nothing. Versioning >will need to extend to 3 numbers, so the next would be 8.4.0. Every
Though I still can not catch up with all email, in my understanding the next version would be 8.3.0. Actually http://www.nuttx.org/Documentation/NuttX.html says the current version is 8.2, however I found typos in ReleaseNotes in nuttx repo which says '133nd ... Version 8.3'. Should I send a PR to fix these typos? NuttX-8.2 Release Notes ------------------------ The 133nd release of NuttX, Version 8.3, was made on November 16, 2019, and is available for download from the Bitbucket.org website. Note that release consists of two tarballs: nuttx-8.2.tar.gz and apps-8.2.tar.gz. These are available from: Masayuki 2020年1月13日(月) 22:13 Gregory Nutt <spudan...@gmail.com>: > > > I think once the workflow is complete we should froze the master and > > keep accepting patch into dev branch. This is my point of view, I > > don't know if we will implement it. > > I think we should create a release branch and freeze nothing. Versioning > will need to extend to 3 numbers, so the next would be 8.4.0. Every > release will have to live on a branch with multiple release candidates > up to the released version, perhaps tagged like nuttx-8.4.0-rc1. If > bugs are found after the release, the code could be re-released as 8.4.1 > and the bugfix merged back to main. > > Greg > > >
