| Message ID | 1454374007-29913-1-git-send-email-mike.holmes@linaro.org |
|---|---|
| State | New |
| Headers | show |
On Mon, Feb 1, 2016 at 6:46 PM, Mike Holmes <mike.holmes@linaro.org> wrote: > Signed-off-by: Mike Holmes <mike.holmes@linaro.org> > --- > doc/process-guide/release-guide.adoc | 12 ++++++++++++ > 1 file changed, 12 insertions(+) > > diff --git a/doc/process-guide/release-guide.adoc > b/doc/process-guide/release-guide.adoc > index 60ef769..9a99c5a 100644 > --- a/doc/process-guide/release-guide.adoc > +++ b/doc/process-guide/release-guide.adoc > @@ -138,6 +138,18 @@ made every month if sufficient change has accumulated. > === Implementation (Impl) === > Platform specific free form text relating to the version. > > +=== Long Term Stable (LTS) === > +Long term stable releases are picked by the steering committee. > This should be clarified as referring to LNG developed and maintained releases. We don't want to give the impression that the LNG-SC speaks for any other ODP implementations. > +When the API in master is considered an LTS candidate it will be tagged > with a > +release name and RC1 for the initial release candidate. > + > +* This release will be branched so that development may continue on > master. > +* The release candidate will continue incrementing as necessary until a > minimum > +of two hardware platforms are able to pass the validation suite, at this > point > +the API is considered stable and it will be tagged as the long term > stable API. > +* This stable branch will receive bug fixes for the LNG supported > platforms for > +a minimum of one year. > + > == Deprecating part of the API > Deleting or changing the published API follows the normal > <<anchor-1,process>>, with the following additional rules: > > -- > 2.5.0 > > _______________________________________________ > lng-odp mailing list > lng-odp@lists.linaro.org > https://lists.linaro.org/mailman/listinfo/lng-odp >
On 1 February 2016 at 19:49, Bill Fischofer <bill.fischofer@linaro.org> wrote: > > > On Mon, Feb 1, 2016 at 6:46 PM, Mike Holmes <mike.holmes@linaro.org> > wrote: > >> Signed-off-by: Mike Holmes <mike.holmes@linaro.org> >> --- >> doc/process-guide/release-guide.adoc | 12 ++++++++++++ >> 1 file changed, 12 insertions(+) >> >> diff --git a/doc/process-guide/release-guide.adoc >> b/doc/process-guide/release-guide.adoc >> index 60ef769..9a99c5a 100644 >> --- a/doc/process-guide/release-guide.adoc >> +++ b/doc/process-guide/release-guide.adoc >> @@ -138,6 +138,18 @@ made every month if sufficient change has >> accumulated. >> === Implementation (Impl) === >> Platform specific free form text relating to the version. >> >> +=== Long Term Stable (LTS) === >> +Long term stable releases are picked by the steering committee. >> > > This should be clarified as referring to LNG developed and maintained > releases. We don't want to give the impression that the LNG-SC speaks for > any other ODP implementations. > True, and further then I will try to make it clearer that they pick the stable API and not really the implementations at all > > >> +When the API in master is considered an LTS candidate it will be tagged >> with a >> +release name and RC1 for the initial release candidate. >> + >> +* This release will be branched so that development may continue on >> master. >> +* The release candidate will continue incrementing as necessary until a >> minimum >> +of two hardware platforms are able to pass the validation suite, at this >> point >> +the API is considered stable and it will be tagged as the long term >> stable API. >> +* This stable branch will receive bug fixes for the LNG supported >> platforms for >> +a minimum of one year. >> + >> == Deprecating part of the API >> Deleting or changing the published API follows the normal >> <<anchor-1,process>>, with the following additional rules: >> >> -- >> 2.5.0 >> >> _______________________________________________ >> lng-odp mailing list >> lng-odp@lists.linaro.org >> https://lists.linaro.org/mailman/listinfo/lng-odp >> > > -- Mike Holmes Technical Manager - Linaro Networking Group Linaro.org <http://www.linaro.org/> *│ *Open source software for ARM SoCs "Work should be fun and collborative, the rest follows"
diff --git a/doc/process-guide/release-guide.adoc b/doc/process-guide/release-guide.adoc index 60ef769..9a99c5a 100644 --- a/doc/process-guide/release-guide.adoc +++ b/doc/process-guide/release-guide.adoc @@ -138,6 +138,18 @@ made every month if sufficient change has accumulated. === Implementation (Impl) === Platform specific free form text relating to the version. +=== Long Term Stable (LTS) === +Long term stable releases are picked by the steering committee. +When the API in master is considered an LTS candidate it will be tagged with a +release name and RC1 for the initial release candidate. + +* This release will be branched so that development may continue on master. +* The release candidate will continue incrementing as necessary until a minimum +of two hardware platforms are able to pass the validation suite, at this point +the API is considered stable and it will be tagged as the long term stable API. +* This stable branch will receive bug fixes for the LNG supported platforms for +a minimum of one year. + == Deprecating part of the API Deleting or changing the published API follows the normal <<anchor-1,process>>, with the following additional rules:
Signed-off-by: Mike Holmes <mike.holmes@linaro.org> --- doc/process-guide/release-guide.adoc | 12 ++++++++++++ 1 file changed, 12 insertions(+)