Re: [Mesa-dev] [PATCH] docs: complete the calendar and release schedule documentation
On Mon, 2019-01-07 at 19:04 +0200, Andres Gomez wrote: > As suggested by Emil Velikov. > > Cc: Dylan Baker > Cc: Juan A. Suarez > Cc: Emil Velikov > Signed-off-by: Andres Gomez > --- > docs/release-calendar.html | 10 ++ > docs/releasing.html| 14 -- > 2 files changed, 22 insertions(+), 2 deletions(-) Acked-by: Juan A. Suarez > > 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. > > +Regular updates will ensure that the schedule for the current and the > +next two feature releases are shown in the table. > + > +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. > + > +The way the release schedule works is > +explained here. > + > Take a look target="_parent">here > if you'd like to nominate a patch in the next stable release. > > 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: > > > Releases should happen on Wednesdays. Delays can occur although those > -should be keep to a minimum. > +should be kept to a minimum. > > -See our calendar for the > +See our calendar > +for information about how the release schedule is planned, and the > date and other details for individual releases. > > > @@ -67,6 +68,9 @@ date and other details for individual releases. > Available approximately every three months. > Initial timeplan available 2-4 weeks before the planned branchpoint (rc1) > on the mesa-announce@ mailing list. > +Typically, the final release will happen after 4 > +candidates. Additional ones may be needed in order to resolve blocking > +regressions, though. > A pre-release announcement should be available > approximately 24 hours before the final (non-rc) release. > > @@ -84,6 +88,12 @@ Note: There is one or two releases overlap when changing > branches. For example: > > 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. > + > +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 calendar with > +additional bug fix releases of the current stable branch. > > > ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] [PATCH] docs: complete the calendar and release schedule documentation
On January 7, 2019 5:07:34 PM UTC, Andres Gomez wrote: > As suggested by Emil Velikov. > > Cc: Dylan Baker > Cc: Juan A. Suarez > Cc: Emil Velikov > Signed-off-by: Andres Gomez Reviewed-by: Eric Engestrom > --- > 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. > > +Regular updates will ensure that the schedule for the current and the > +next two feature releases are shown in the table. > + > +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. > + > +The way the release schedule works is > +explained target="_parent">here. > + > Take a look target="_parent">here > if you'd like to nominate a patch in the next stable release. > > 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: > > > Releases should happen on Wednesdays. Delays can occur although those > -should be keep to a minimum. > +should be kept to a minimum. > > -See our calendar > for the > +See our calendar > +for information about how the release schedule is planned, and the > date and other details for individual releases. > > > @@ -67,6 +68,9 @@ date and other details for individual releases. > Available approximately every three months. > Initial timeplan available 2-4 weeks before the planned > branchpoint (rc1) > on the mesa-announce@ mailing list. > +Typically, the final release will happen after 4 > +candidates. Additional ones may be needed in order to resolve > blocking > +regressions, though. > A pre-release announcement should be > available > approximately 24 hours before the final (non-rc) release. > > @@ -84,6 +88,12 @@ Note: There is one or two releases overlap when > changing branches. For example: > > 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. > + > +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 calendar > with > +additional bug fix releases of the current stable branch. > > > ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] [PATCH] docs: complete the calendar and release schedule documentation
Quoting Andres Gomez (2019-01-07 09:04:34) > As suggested by Emil Velikov. > > Cc: Dylan Baker > Cc: Juan A. Suarez > Cc: Emil Velikov > Signed-off-by: Andres Gomez > --- > 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. > > +Regular updates will ensure that the schedule for the current and the > +next two feature releases are shown in the table. > + > +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. > + > +The way the release schedule works is > +explained here. > + > Take a look target="_parent">here > if you'd like to nominate a patch in the next stable release. > > 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: > > > Releases should happen on Wednesdays. Delays can occur although those > -should be keep to a minimum. > +should be kept to a minimum. > > -See our calendar for the > +See our calendar > +for information about how the release schedule is planned, and the > date and other details for individual releases. > > > @@ -67,6 +68,9 @@ date and other details for individual releases. > Available approximately every three months. > Initial timeplan available 2-4 weeks before the planned branchpoint (rc1) > on the mesa-announce@ mailing list. > +Typically, the final release will happen after 4 > +candidates. Additional ones may be needed in order to resolve blocking > +regressions, though. > A pre-release announcement should be available > approximately 24 hours before the final (non-rc) release. > > @@ -84,6 +88,12 @@ Note: There is one or two releases overlap when changing > branches. For example: > > 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. > + > +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 calendar with > +additional bug fix releases of the current stable branch. > > > > -- > 2.18.0 > Acked-by: Dylan Baker signature.asc Description: signature ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [PATCH] docs: complete the calendar and release schedule documentation
As suggested by Emil Velikov. Cc: Dylan Baker Cc: Juan A. Suarez Cc: Emil Velikov Signed-off-by: Andres Gomez --- 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. +Regular updates will ensure that the schedule for the current and the +next two feature releases are shown in the table. + +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. + +The way the release schedule works is +explained here. + Take a look here if you'd like to nominate a patch in the next stable release. 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: Releases should happen on Wednesdays. Delays can occur although those -should be keep to a minimum. +should be kept to a minimum. -See our calendar for the +See our calendar +for information about how the release schedule is planned, and the date and other details for individual releases. @@ -67,6 +68,9 @@ date and other details for individual releases. Available approximately every three months. Initial timeplan available 2-4 weeks before the planned branchpoint (rc1) on the mesa-announce@ mailing list. +Typically, the final release will happen after 4 +candidates. Additional ones may be needed in order to resolve blocking +regressions, though. A pre-release announcement should be available approximately 24 hours before the final (non-rc) release. @@ -84,6 +88,12 @@ Note: There is one or two releases overlap when changing branches. For example: 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. + +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 calendar with +additional bug fix releases of the current stable branch. -- 2.18.0 ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
