Hi Adam, 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.
Also we need to review all the committed patch to the master to create the Changelog/Release Notes. This should be the hard part. BR, Alan On 1/12/20, Adam Feuer <a...@starcat.io> wrote: > What needs to be done to move closer to release? > > On other projects I've been on, we froze the master branch except for > bugfix commits (did not merge new features), and iterated until things > stabilized. Can we do that here? > > As to having a release manager, what's involved in that? Is there a role > description somewhere? > > cheer > adam > > > > On Sun, Jan 12, 2020 at 4:44 PM Gregory Nutt <spudan...@gmail.com> wrote: > >> >> > I have ran the build tests and do not know of any other cases like >> > this. ... >> >> That needs clarification. I have been starting the build tests everyday >> for the past weeks, but there has been no successful, complete run of >> the ARM builds in the past 3 weeks. The build has been broken every day >> for the past three weeks and the breakage appears to be getting worse, >> not better. >> >> This weekend was the due date for the 8.4 release of NuttX. That has >> now gone by. I will not be doing any further releases. That is now the >> responsibility of the PPMC. The next NuttX release will be the first >> Apache release. >> >> When should we do this first Apache release? How do we do this? Who is >> the release manager? (hint: not me) Since the breakage is coming on a >> daily basis, how/when can we get a stable enough system to even consider >> a release. >> >> I required two weeks of stable builds with no new bugs reported before a >> release. We are not ready to do a release right now. I don't think I >> have ever seen the OS so unstable as it is right now. It does not build >> correctly. There are more and more reports of old stable functionality >> that is now broken. I have no idea how to get there... at least not >> without some proper workflow definition and some qualification tools in >> place. >> >> Folks, we are destroying this OS. >> >> Greg >> >> >> > > -- > Adam Feuer <a...@starcat.io> >
