Thank you Nathan for this detailed procedure. I think the date is reasonable. Even though personally I was hoping to have a release earlier. But given all the steps outlined, I find it reasonable. That's enough time to prepare and for contributors to get last-minute changes ready. Let's please get everyone's opinion on this.
> (2) Soak period until April 20. I recommend we post a heads-up to the > Incubator General mailing list that we are beginning our first > release and there will be a vote soon, and in that email, ask very > nicely for IPMC members to kindly overlook what we're doing, so > that we won't have nasty surprises later!! Is there any project doing this already? We will have to put the release into a vote for the IPMC to approve. I used to check their feedback. Here are some points: - Have incubating in name. - Disclaimer, license and notice. - Signature and hashes. - Can compile from source. With the help of our mentors we can nail these before calling a vote in the incubator general list. On Sun, Mar 29, 2020 at 5:14 PM Nathan Hartman <hartman.nat...@gmail.com> wrote: > > On Sun, Mar 29, 2020 at 11:44 AM Gregory Nutt <spudan...@gmail.com> wrote: > > Do we plan to generate Release Notes? In my experience that is the most > > difficult part of the release (the rest is fun). Abdelatif tells me that > > there are 1051 commits. That is a much lower number that I expecteded, > > lower than most old 2 month cycles, but probably still more than anyone > > really wants to dig into in detail. > > > > We can control this level of effort. Perhaps we just want to list major > > new architectures and boards supported. And any major new OS features? > > That would be a relatively low effort. it would be nice to list the > > major bugs that have been fixed but I don't know of any easy way to get > > that. > > I'll start a new separate thread to discuss release notes... > > Nathan
