On January 7, 2019 5:07:34 PM UTC, Andres Gomez <ago...@igalia.com> wrote: > As suggested by Emil Velikov. > > Cc: Dylan Baker <dylan.c.ba...@intel.com> > Cc: Juan A. Suarez <jasua...@igalia.com> > Cc: Emil Velikov <emil.veli...@collabora.com> > Signed-off-by: Andres Gomez <ago...@igalia.com>
Reviewed-by: Eric Engestrom <e...@engestrom.ch> > --- > docs/release-calendar.html | 10 ++++++++++ > docs/releasing.html | 14 ++++++++++++-- > 2 files changed, 22 insertions(+), 2 deletions(-) > > diff --git a/docs/release-calendar.html b/docs/release-calendar.html > index afef899b0e0..3f4e1e9d8b9 100644 > --- a/docs/release-calendar.html > +++ b/docs/release-calendar.html > @@ -23,6 +23,16 @@ Mesa provides feature/development and stable > releases. > The table below lists the date and release manager that is expected to > do the > specific release. > <br> > +Regular updates will ensure that the schedule for the current and the > +next two feature releases are shown in the table. > +<br> > +In order to keep the whole releasing team up to date with the tools > +used, best practices and other details, the member in charge of the > +next feature release will be in constant rotation. > +<br> > +The way the release schedule works is > +explained <a href="releasing.html#schedule" > target="_parent">here</a>. > +<br> > Take a look <a href="submittingpatches.html#criteria" > target="_parent">here</a> > if you'd like to nominate a patch in the next stable release. > </p> > diff --git a/docs/releasing.html b/docs/releasing.html > index e4c770f9186..851bbf58670 100644 > --- a/docs/releasing.html > +++ b/docs/releasing.html > @@ -56,9 +56,10 @@ For example: > > <p> > Releases should happen on Wednesdays. Delays can occur although those > -should be keep to a minimum. > +should be kept to a minimum. > <br> > -See our <a href="release-calendar.html" target="_parent">calendar</a> > for the > +See our <a href="release-calendar.html" target="_parent">calendar</a> > +for information about how the release schedule is planned, and the > date and other details for individual releases. > </p> > > @@ -67,6 +68,9 @@ date and other details for individual releases. > <li>Available approximately every three months. > <li>Initial timeplan available 2-4 weeks before the planned > branchpoint (rc1) > on the mesa-announce@ mailing list. > +<li>Typically, the final release will happen after 4 > +candidates. Additional ones may be needed in order to resolve > blocking > +regressions, though. > <li>A <a href="#prerelease">pre-release</a> announcement should be > available > approximately 24 hours before the final (non-rc) release. > </ul> > @@ -84,6 +88,12 @@ Note: There is one or two releases overlap when > changing branches. For example: > <br> > The final release from the 12.0 series Mesa 12.0.5 will be out around > the same > time (or shortly after) 13.0.1 is out. > +<br> > +This also involves that, as a final release may be delayed due to the > +need of additional candidates to solve some blocking regression(s), > +the release manager might have to update > +the <a href="release-calendar.html" target="_parent">calendar</a> > with > +additional bug fix releases of the current stable branch. > </p> > > _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev