I am unclear about the build status and what has been added and if all the configs are in the test list. As I read the email from Xiang Xiao - all the builds do not build yet. I thought in the past ALL the builds were built before a release.
-----Original Message----- From: Abdelatif Guettouche [mailto:abdelatif.guettou...@gmail.com] Sent: Thursday, February 27, 2020 6:10 AM To: dev@nuttx.apache.org Subject: Re: Progress on making a release With the nightly build in place, we would want to wait for some clean builds to consider a release. We want to make sure that the code is stable enough. However, we can make progress by taking care of some of Apache's requirements. Justin, summarized what we should do in an earlier thread. [1] First thing is to created DISCLAIMER, LICENSE and NOTICE files. I created a draft PR (https://github.com/apache/incubator-nuttx/pull/392) where I added these files. Please check it and share your thoughts. We also need to define our release process. Something like: Create a branch from master that will serve as a release candidate. Make the necessary modifications in preparation of a release (update release notes, documentation, etc.) Accept only critical bug fixes to the RC, other PRs should still go to master. This is not a release process proposition, just a draft that I'm writing in a hurry. We also need to agree on versioning numbers and how bugs found after the release should be incorporated. Please share your thoughts. 1. https://lists.apache.org/thread.html/r18435832d8730b14abe4715d74a8307b152d753494208843c2df499a%40%3Cdev.nuttx.apache.org%3E On Thu, Feb 27, 2020 at 11:16 AM Xiang Xiao <xiaoxiang781...@gmail.com> wrote: > > As I remember correctly, Brennan want to take the release manager role > to finish the first release. > > On Thu, Feb 27, 2020 at 9:24 AM Nathan Hartman <hartman.nat...@gmail.com> > wrote: > > > > On Wed, Feb 26, 2020 at 8:05 PM Justin Mclean <jus...@classsoftware.com> > > wrote: > > > Where is the project at in moving forward to make it’s next release? > > > > I think we should begin to plan our release procedures and release > > schedule. > > > > The first thing we need is a Release Manager (RM). This need not be a > > fixed role; we could have a different volunteer for the RM role for > > each release, or one person could choose to be RM continuously until > > they can't or don't wish to do it anymore. > > > > Do we have any volunteers? > > > > Cheers, > > Nathan
