Eric Engestrom <e...@engestrom.ch> writes: > On 2019-07-31 at 09:38, Emil Velikov <emil.l.veli...@gmail.com> wrote: >> Hi all, >> >> Here is the tentative release plan for 19.2.0. >> >> As many of you are well aware, it's time to the next branch point. >> The calendar is already updated, so these are the tentative dates: >> >> Aug 06 2019 - Feature freeze/Release candidate 1 >> Aug 13 2019 - Release candidate 2 >> Aug 20 2019 - Release candidate 3 >> Aug 27 2019 - Release candidate 4/final release >> >> This gives us around 1 week until the branch point. >> >> Note: In the spirit of keeping things clearer and more transparent, we >> will be keeping track of any features planned for the release in >> Bugzilla [1]. >> >> Do add a separate "Depends on" for each work you have planned. >> Alternatively you can reply to this email and I'll add them for you. >> >> [1] https://bugs.freedesktop.org/show_bug.cgi?id=111265 > > Thanks! > > As per previous discussions (I don't remember where, sorry) as well as > internal discussions, I think we should add all currently open > regressions since 19.1 as blockers for this release.
My understanding is that the "feature tracker" blocks the creation of the release branchpoint. A separate "release tracker" blocks the release of 19.2.0. Unfixed regressions go on the "release tracker", not the "feature tracker". We backport bug fixes to release branches, but we don't backport features. > We should also add that to the procedure in our docs; I'll do that > later today if nobody beats me to it. > _______________________________________________ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/mesa-dev _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
