Re: [Avocado-devel] [RFC v4]: Long Term Stability (was Avocado maintainability and integration with avocado-vt)

[Cleber Rosa]

On 04/28/2017 11:17 AM, Jeff Nelson wrote:
> 
> 
> Maybe I'm being pedantic, but how about some visual separation between
> the sprint release and the things that follow? It looks to me as if
> one could interpret everything under a numbered sprint release as
> happening at the same time, when in fact we want to point out that
> (a) bug discovery can happen at any time
> (b) the bugfix occurs next
> (c) the severity of the defect determines the timing of the release
> (c.1) moderate and minor bugfixes to lts branches are held until the
>   next sprint release
> (c.2) critical bugs are released asynchronously, without waiting for the
>   next sprint release.
> 
> 53
>   * sprint release 53.0
> 
> * moderate bug that affects users of master, 52lts and 36lts is found
> * fix is added to master and backported to 52lts and 36lts
> 
> 54
>   * sprint release 54.0 **AND** 36lts release 36.5 **AND** 52lts release 52.1
> 
> * minor bug that affects users of master and 52lts is found
> * fix is added to master and backported to 52lts
> 
> 55
>   * sprint release 55.0 **AND** 52lts release 52.2
> 
> * critical bug is found that affects users of 52lts *only*
> * fix is made to 52lts and 52lts release 52.3 is immediately announced
> 
> I dunno; just something to think about.
> 
> -Jeff
> 

This is how I managed (I hope!) to accommodate your suggestions:

---

Timeline example


Consider the release numbers as date markers.  The bullet points
beneath them are information about the release itself or events that
can happen anytime between one release and the other.  Assume each
sprint is taking 3 weeks.

 36.0
   * **LTS** release (the only LTS release available at the time of
 writing)

 37.0 .. 49.0
   * sprint releases
   * 36.1 LTS release
   * 36.2 LTS release
   * 36.3 LTS release
   * 36.4 LTS release

 50.0
   * sprint release
   * start preparing a LTS release, so 51.0 will be a **beta LTS**

 51.0
   * sprint release
   * **beta LTS** release

 52.0
   * **LTS** release
   * 52lts branch is created
   * packages go into LTS repo
   * both **36.x LTS** and **52.x LTS** maintained from this point on

 53.0
   * sprint release
   * minor bug that affects 52.0 is found, fix gets added to master and
 52lts branches
   * bug does **not** affect 36.x LTS, so a backport is **not** added to
 the 36lts branch

 54.0
   * sprint release 54.0
   * LTS release 52.1
   * minor bug that also affects 52.x LTS and 36.x LTS is found, fix
 gets added to master, 52lts and 36lts branches

 55.0
   * sprint release
   * LTS release 36.5
   * LTS release 52.2
   * critical bug that affects 52.2 *only* is found, fix gets added to
 52lts and **52.3 LTS is immediately released**

 56.0
  * sprint release

 57.0
  * sprint release

 58.0
  * sprint release

 59.0
  * sprint release
  * EOL for **36.x LTS** (18 months since the release of 36.0), 36lts
branch is frozen permanently.

A few points are worth taking notice here:

 * Multiple LTS releases can co-exist before EOL

 * Bug discovery can happen at any time

 * The bugfix occurs ASAP after its discovery

 * The severity of the defect determines the timing of the release

   - moderate and minor bugfixes to lts branches are held until the
 next sprint release

   - critical bugs are released asynchronously, without waiting for
 the next sprint release


---

Regards,

-- 
Cleber Rosa
[ Sr Software Engineer - Virtualization Team - Red Hat ]
[ Avocado Test Framework - avocado-framework.github.io ]
[  7ABB 96EB 8B46 B94D 5E0F  E9BB 657E 8D33 A5F2 09F3  ]



signature.asc
Description: OpenPGP digital signature

Re: [Avocado-devel] [RFC v4]: Long Term Stability (was Avocado maintainability and integration with avocado-vt)

[Cleber Rosa]

On 04/28/2017 11:17 AM, Jeff Nelson wrote:
> On Fri, 28 Apr 2017 15:58:11 +0200
> Amador Segundo  wrote:
> 
>> On Thu, Apr 27, 2017 at 5:15 PM, Cleber Rosa  wrote:
>>>
>>>
>>> On 04/27/2017 04:04 AM, Amador Segundo wrote:  
 On Thu, Apr 27, 2017 at 1:07 AM, Cleber Rosa  wrote:  
> ==
>  RFC: Long Term Stability
> ==
>
> This RFC contains proposals and clarifications regarding the
> maintenance and release processes of Avocado.
>
> We understand there are multiple teams currently depending on the
> stability of Avocado and we don't want their work to be disrupted by
> incompatibilities nor instabilities in new releases.
>
> This version is a minor update to previous versions of the same RFC
> (see `Changelog`_) which drove the release of Avocado 36.0 LTS.  The
> Avocado team has plans for a new LTS release in the near future, so
> please consider reading and providing feedback on the proposals here.
>
> TL;DR
> =
>
> We plan to keep the current approach of sprint releases every 3-4
> weeks, but we're introducing "Long Term Stability" releases which
> should be adopted in production environments where users can't keep up
> with frequent upgrades.
>
> Changelog
> =
>
> Changes from `Version 3`_:
>
>  * Converted formatting to REStructuredText
>  * Replaced "me" mentions on version 1 changelog with proper name
>(Ademar Reis)
>  * Renamed section "Misc Details" to `Deployment Details`_
>  * Renamed "avocado-vt" to "Avocado-VT"
>  * Start the timeline example with version 36.0
>  * Be explicit on timeline example that a minor bug did not generate
>an immediate release
>
> Changes from `Version 2`_:
>
>  * Wording changes on second paragraph ("... nor instabilities...")
>  * Clarified on "Introduction" that change of behavior is introduced
>between regular releases
>  * Updated distro versions for which official packages are built
>  * Add more clear explanation on official packages on the various
>hardware platforms
>  * Used more recent version numbers as examples, and the planned
>new LTS version too
>  * Explain how users can get the LTS version when using tools such as
>pip
>  * Simplified the timeline example, with examples that will possibly
>match the future versions and releases
>  * Documented current status of Avocado-VT releases and packages
>
> Changes from `Version 1`_:
>
>  * Changed "Support" to "Stability" and "supported" to "maintained"
>[Jeff Nelson]
>  * Misc improvements and clarifications in the
>supportability/stability statements [Jeff Nelson, Ademar Reis]
>  * Fixed a few typos [Jeff Nelson, Ademar Reis]
>
> Introduction
> 
>
> We make new releases of Avocado every 3-4 weeks on average.  In theory
> at least, we're very careful with backwards compatibility.  We test
> Avocado for regressions and we try to document any issues, so
> upgrading to a new version should be (again, in theory) safe.
>
> But in practice both intended and unintended changes are introduced
> during development, and both can be frustrating for conservative
> users. We also understand it's not feasible for users to upgrade
> Avocado very frequently in a production environment.
>
> The objective of this RFC is to clarify our maintenance practices and
> introduce Long Term Stability (LTS) releases, which are intended to
> solve, or at least mitigate, these problems.
>
>
> Our definition of maintained, or stable
> ===
>
> First of all, Avocado and its sub-projects are provided 'AS IS' and
> WITHOUT ANY WARRANTY, as described in the LICENSE file.
>
> The process described here doesn't imply any commitments or
> promises. It's just a set of best practices and recommendations.
>
> When something is identified as "stable" or "maintained", it means the
> development community makes a conscious effort to keep it working and
> consider reports of bugs and issues as high priorities.  Fixes
> submitted for these issues will also be considered high priorities,
> although they will be accepted only if they pass the general
> acceptance criteria for new contributions (design, quality,
> documentation, testing, etc), at the development team discretion.
>
>
> Maintained projects and platforms
> =
>
> The only maintained project as of today is the Avocado Test Runner,
> including its APIs and core plugins (the contents of the main avocado
> git repository).
>
> Other projects kept 

Re: [Avocado-devel] [RFC v4]: Long Term Stability (was Avocado maintainability and integration with avocado-vt)

[Amador Segundo]

On Thu, Apr 27, 2017 at 5:15 PM, Cleber Rosa  wrote:
>
>
> On 04/27/2017 04:04 AM, Amador Segundo wrote:
>> On Thu, Apr 27, 2017 at 1:07 AM, Cleber Rosa  wrote:
>>> ==
>>>  RFC: Long Term Stability
>>> ==
>>>
>>> This RFC contains proposals and clarifications regarding the
>>> maintenance and release processes of Avocado.
>>>
>>> We understand there are multiple teams currently depending on the
>>> stability of Avocado and we don't want their work to be disrupted by
>>> incompatibilities nor instabilities in new releases.
>>>
>>> This version is a minor update to previous versions of the same RFC
>>> (see `Changelog`_) which drove the release of Avocado 36.0 LTS.  The
>>> Avocado team has plans for a new LTS release in the near future, so
>>> please consider reading and providing feedback on the proposals here.
>>>
>>> TL;DR
>>> =
>>>
>>> We plan to keep the current approach of sprint releases every 3-4
>>> weeks, but we're introducing "Long Term Stability" releases which
>>> should be adopted in production environments where users can't keep up
>>> with frequent upgrades.
>>>
>>> Changelog
>>> =
>>>
>>> Changes from `Version 3`_:
>>>
>>>  * Converted formatting to REStructuredText
>>>  * Replaced "me" mentions on version 1 changelog with proper name
>>>(Ademar Reis)
>>>  * Renamed section "Misc Details" to `Deployment Details`_
>>>  * Renamed "avocado-vt" to "Avocado-VT"
>>>  * Start the timeline example with version 36.0
>>>  * Be explicit on timeline example that a minor bug did not generate
>>>an immediate release
>>>
>>> Changes from `Version 2`_:
>>>
>>>  * Wording changes on second paragraph ("... nor instabilities...")
>>>  * Clarified on "Introduction" that change of behavior is introduced
>>>between regular releases
>>>  * Updated distro versions for which official packages are built
>>>  * Add more clear explanation on official packages on the various
>>>hardware platforms
>>>  * Used more recent version numbers as examples, and the planned
>>>new LTS version too
>>>  * Explain how users can get the LTS version when using tools such as
>>>pip
>>>  * Simplified the timeline example, with examples that will possibly
>>>match the future versions and releases
>>>  * Documented current status of Avocado-VT releases and packages
>>>
>>> Changes from `Version 1`_:
>>>
>>>  * Changed "Support" to "Stability" and "supported" to "maintained"
>>>[Jeff Nelson]
>>>  * Misc improvements and clarifications in the
>>>supportability/stability statements [Jeff Nelson, Ademar Reis]
>>>  * Fixed a few typos [Jeff Nelson, Ademar Reis]
>>>
>>> Introduction
>>> 
>>>
>>> We make new releases of Avocado every 3-4 weeks on average.  In theory
>>> at least, we're very careful with backwards compatibility.  We test
>>> Avocado for regressions and we try to document any issues, so
>>> upgrading to a new version should be (again, in theory) safe.
>>>
>>> But in practice both intended and unintended changes are introduced
>>> during development, and both can be frustrating for conservative
>>> users. We also understand it's not feasible for users to upgrade
>>> Avocado very frequently in a production environment.
>>>
>>> The objective of this RFC is to clarify our maintenance practices and
>>> introduce Long Term Stability (LTS) releases, which are intended to
>>> solve, or at least mitigate, these problems.
>>>
>>>
>>> Our definition of maintained, or stable
>>> ===
>>>
>>> First of all, Avocado and its sub-projects are provided 'AS IS' and
>>> WITHOUT ANY WARRANTY, as described in the LICENSE file.
>>>
>>> The process described here doesn't imply any commitments or
>>> promises. It's just a set of best practices and recommendations.
>>>
>>> When something is identified as "stable" or "maintained", it means the
>>> development community makes a conscious effort to keep it working and
>>> consider reports of bugs and issues as high priorities.  Fixes
>>> submitted for these issues will also be considered high priorities,
>>> although they will be accepted only if they pass the general
>>> acceptance criteria for new contributions (design, quality,
>>> documentation, testing, etc), at the development team discretion.
>>>
>>>
>>> Maintained projects and platforms
>>> =
>>>
>>> The only maintained project as of today is the Avocado Test Runner,
>>> including its APIs and core plugins (the contents of the main avocado
>>> git repository).
>>>
>>> Other projects kept under the "Avocado Umbrella" in github may be
>>> maintained by different teams (e.g.: Avocado-VT) or be considered
>>> experimental (e.g.: avocado-server and avocado-virt).
>>>
>>> More about Avocado-VT in its own section further down.
>>>
>>> As a general rule, fixes and bug reports for Avocado when running in
>>> any modern Linux distribution are welcome.

Re: [Avocado-devel] [RFC v4]: Long Term Stability (was Avocado maintainability and integration with avocado-vt)

[Cleber Rosa]

On 04/27/2017 04:04 AM, Amador Segundo wrote:
> On Thu, Apr 27, 2017 at 1:07 AM, Cleber Rosa  wrote:
>> ==
>>  RFC: Long Term Stability
>> ==
>>
>> This RFC contains proposals and clarifications regarding the
>> maintenance and release processes of Avocado.
>>
>> We understand there are multiple teams currently depending on the
>> stability of Avocado and we don't want their work to be disrupted by
>> incompatibilities nor instabilities in new releases.
>>
>> This version is a minor update to previous versions of the same RFC
>> (see `Changelog`_) which drove the release of Avocado 36.0 LTS.  The
>> Avocado team has plans for a new LTS release in the near future, so
>> please consider reading and providing feedback on the proposals here.
>>
>> TL;DR
>> =
>>
>> We plan to keep the current approach of sprint releases every 3-4
>> weeks, but we're introducing "Long Term Stability" releases which
>> should be adopted in production environments where users can't keep up
>> with frequent upgrades.
>>
>> Changelog
>> =
>>
>> Changes from `Version 3`_:
>>
>>  * Converted formatting to REStructuredText
>>  * Replaced "me" mentions on version 1 changelog with proper name
>>(Ademar Reis)
>>  * Renamed section "Misc Details" to `Deployment Details`_
>>  * Renamed "avocado-vt" to "Avocado-VT"
>>  * Start the timeline example with version 36.0
>>  * Be explicit on timeline example that a minor bug did not generate
>>an immediate release
>>
>> Changes from `Version 2`_:
>>
>>  * Wording changes on second paragraph ("... nor instabilities...")
>>  * Clarified on "Introduction" that change of behavior is introduced
>>between regular releases
>>  * Updated distro versions for which official packages are built
>>  * Add more clear explanation on official packages on the various
>>hardware platforms
>>  * Used more recent version numbers as examples, and the planned
>>new LTS version too
>>  * Explain how users can get the LTS version when using tools such as
>>pip
>>  * Simplified the timeline example, with examples that will possibly
>>match the future versions and releases
>>  * Documented current status of Avocado-VT releases and packages
>>
>> Changes from `Version 1`_:
>>
>>  * Changed "Support" to "Stability" and "supported" to "maintained"
>>[Jeff Nelson]
>>  * Misc improvements and clarifications in the
>>supportability/stability statements [Jeff Nelson, Ademar Reis]
>>  * Fixed a few typos [Jeff Nelson, Ademar Reis]
>>
>> Introduction
>> 
>>
>> We make new releases of Avocado every 3-4 weeks on average.  In theory
>> at least, we're very careful with backwards compatibility.  We test
>> Avocado for regressions and we try to document any issues, so
>> upgrading to a new version should be (again, in theory) safe.
>>
>> But in practice both intended and unintended changes are introduced
>> during development, and both can be frustrating for conservative
>> users. We also understand it's not feasible for users to upgrade
>> Avocado very frequently in a production environment.
>>
>> The objective of this RFC is to clarify our maintenance practices and
>> introduce Long Term Stability (LTS) releases, which are intended to
>> solve, or at least mitigate, these problems.
>>
>>
>> Our definition of maintained, or stable
>> ===
>>
>> First of all, Avocado and its sub-projects are provided 'AS IS' and
>> WITHOUT ANY WARRANTY, as described in the LICENSE file.
>>
>> The process described here doesn't imply any commitments or
>> promises. It's just a set of best practices and recommendations.
>>
>> When something is identified as "stable" or "maintained", it means the
>> development community makes a conscious effort to keep it working and
>> consider reports of bugs and issues as high priorities.  Fixes
>> submitted for these issues will also be considered high priorities,
>> although they will be accepted only if they pass the general
>> acceptance criteria for new contributions (design, quality,
>> documentation, testing, etc), at the development team discretion.
>>
>>
>> Maintained projects and platforms
>> =
>>
>> The only maintained project as of today is the Avocado Test Runner,
>> including its APIs and core plugins (the contents of the main avocado
>> git repository).
>>
>> Other projects kept under the "Avocado Umbrella" in github may be
>> maintained by different teams (e.g.: Avocado-VT) or be considered
>> experimental (e.g.: avocado-server and avocado-virt).
>>
>> More about Avocado-VT in its own section further down.
>>
>> As a general rule, fixes and bug reports for Avocado when running in
>> any modern Linux distribution are welcome.
>>
>> But given the limited capacity of the development team, packaged
>> versions of Avocado will be tested and maintained only for the
>> following Linux distributions:
>>
>>  * RHEL 7.x 

Re: [Avocado-devel] [RFC v4]: Long Term Stability (was Avocado maintainability and integration with avocado-vt)

[Amador Segundo]

On Thu, Apr 27, 2017 at 10:04 AM, Amador Segundo  wrote:
> On Thu, Apr 27, 2017 at 1:07 AM, Cleber Rosa  wrote:
>> ==
>>  RFC: Long Term Stability
>> ==
>>
>> This RFC contains proposals and clarifications regarding the
>> maintenance and release processes of Avocado.
>>
>> We understand there are multiple teams currently depending on the
>> stability of Avocado and we don't want their work to be disrupted by
>> incompatibilities nor instabilities in new releases.
>>
>> This version is a minor update to previous versions of the same RFC
>> (see `Changelog`_) which drove the release of Avocado 36.0 LTS.  The
>> Avocado team has plans for a new LTS release in the near future, so
>> please consider reading and providing feedback on the proposals here.
>>
>> TL;DR
>> =
>>
>> We plan to keep the current approach of sprint releases every 3-4
>> weeks, but we're introducing "Long Term Stability" releases which
>> should be adopted in production environments where users can't keep up
>> with frequent upgrades.
>>
>> Changelog
>> =
>>
>> Changes from `Version 3`_:
>>
>>  * Converted formatting to REStructuredText
>>  * Replaced "me" mentions on version 1 changelog with proper name
>>(Ademar Reis)
>>  * Renamed section "Misc Details" to `Deployment Details`_
>>  * Renamed "avocado-vt" to "Avocado-VT"
>>  * Start the timeline example with version 36.0
>>  * Be explicit on timeline example that a minor bug did not generate
>>an immediate release
>>
>> Changes from `Version 2`_:
>>
>>  * Wording changes on second paragraph ("... nor instabilities...")
>>  * Clarified on "Introduction" that change of behavior is introduced
>>between regular releases
>>  * Updated distro versions for which official packages are built
>>  * Add more clear explanation on official packages on the various
>>hardware platforms
>>  * Used more recent version numbers as examples, and the planned
>>new LTS version too
>>  * Explain how users can get the LTS version when using tools such as
>>pip
>>  * Simplified the timeline example, with examples that will possibly
>>match the future versions and releases
>>  * Documented current status of Avocado-VT releases and packages
>>
>> Changes from `Version 1`_:
>>
>>  * Changed "Support" to "Stability" and "supported" to "maintained"
>>[Jeff Nelson]
>>  * Misc improvements and clarifications in the
>>supportability/stability statements [Jeff Nelson, Ademar Reis]
>>  * Fixed a few typos [Jeff Nelson, Ademar Reis]
>>
>> Introduction
>> 
>>
>> We make new releases of Avocado every 3-4 weeks on average.  In theory
>> at least, we're very careful with backwards compatibility.  We test
>> Avocado for regressions and we try to document any issues, so
>> upgrading to a new version should be (again, in theory) safe.
>>
>> But in practice both intended and unintended changes are introduced
>> during development, and both can be frustrating for conservative
>> users. We also understand it's not feasible for users to upgrade
>> Avocado very frequently in a production environment.
>>
>> The objective of this RFC is to clarify our maintenance practices and
>> introduce Long Term Stability (LTS) releases, which are intended to
>> solve, or at least mitigate, these problems.
>>
>>
>> Our definition of maintained, or stable
>> ===
>>
>> First of all, Avocado and its sub-projects are provided 'AS IS' and
>> WITHOUT ANY WARRANTY, as described in the LICENSE file.
>>
>> The process described here doesn't imply any commitments or
>> promises. It's just a set of best practices and recommendations.
>>
>> When something is identified as "stable" or "maintained", it means the
>> development community makes a conscious effort to keep it working and
>> consider reports of bugs and issues as high priorities.  Fixes
>> submitted for these issues will also be considered high priorities,
>> although they will be accepted only if they pass the general
>> acceptance criteria for new contributions (design, quality,
>> documentation, testing, etc), at the development team discretion.
>>
>>
>> Maintained projects and platforms
>> =
>>
>> The only maintained project as of today is the Avocado Test Runner,
>> including its APIs and core plugins (the contents of the main avocado
>> git repository).
>>
>> Other projects kept under the "Avocado Umbrella" in github may be
>> maintained by different teams (e.g.: Avocado-VT) or be considered
>> experimental (e.g.: avocado-server and avocado-virt).
>>
>> More about Avocado-VT in its own section further down.
>>
>> As a general rule, fixes and bug reports for Avocado when running in
>> any modern Linux distribution are welcome.
>>
>> But given the limited capacity of the development team, packaged
>> versions of Avocado will be tested and maintained only for the
>> following Linux 

Re: [Avocado-devel] [RFC v4]: Long Term Stability (was Avocado maintainability and integration with avocado-vt)

[Amador Segundo]

On Thu, Apr 27, 2017 at 1:07 AM, Cleber Rosa  wrote:
> ==
>  RFC: Long Term Stability
> ==
>
> This RFC contains proposals and clarifications regarding the
> maintenance and release processes of Avocado.
>
> We understand there are multiple teams currently depending on the
> stability of Avocado and we don't want their work to be disrupted by
> incompatibilities nor instabilities in new releases.
>
> This version is a minor update to previous versions of the same RFC
> (see `Changelog`_) which drove the release of Avocado 36.0 LTS.  The
> Avocado team has plans for a new LTS release in the near future, so
> please consider reading and providing feedback on the proposals here.
>
> TL;DR
> =
>
> We plan to keep the current approach of sprint releases every 3-4
> weeks, but we're introducing "Long Term Stability" releases which
> should be adopted in production environments where users can't keep up
> with frequent upgrades.
>
> Changelog
> =
>
> Changes from `Version 3`_:
>
>  * Converted formatting to REStructuredText
>  * Replaced "me" mentions on version 1 changelog with proper name
>(Ademar Reis)
>  * Renamed section "Misc Details" to `Deployment Details`_
>  * Renamed "avocado-vt" to "Avocado-VT"
>  * Start the timeline example with version 36.0
>  * Be explicit on timeline example that a minor bug did not generate
>an immediate release
>
> Changes from `Version 2`_:
>
>  * Wording changes on second paragraph ("... nor instabilities...")
>  * Clarified on "Introduction" that change of behavior is introduced
>between regular releases
>  * Updated distro versions for which official packages are built
>  * Add more clear explanation on official packages on the various
>hardware platforms
>  * Used more recent version numbers as examples, and the planned
>new LTS version too
>  * Explain how users can get the LTS version when using tools such as
>pip
>  * Simplified the timeline example, with examples that will possibly
>match the future versions and releases
>  * Documented current status of Avocado-VT releases and packages
>
> Changes from `Version 1`_:
>
>  * Changed "Support" to "Stability" and "supported" to "maintained"
>[Jeff Nelson]
>  * Misc improvements and clarifications in the
>supportability/stability statements [Jeff Nelson, Ademar Reis]
>  * Fixed a few typos [Jeff Nelson, Ademar Reis]
>
> Introduction
> 
>
> We make new releases of Avocado every 3-4 weeks on average.  In theory
> at least, we're very careful with backwards compatibility.  We test
> Avocado for regressions and we try to document any issues, so
> upgrading to a new version should be (again, in theory) safe.
>
> But in practice both intended and unintended changes are introduced
> during development, and both can be frustrating for conservative
> users. We also understand it's not feasible for users to upgrade
> Avocado very frequently in a production environment.
>
> The objective of this RFC is to clarify our maintenance practices and
> introduce Long Term Stability (LTS) releases, which are intended to
> solve, or at least mitigate, these problems.
>
>
> Our definition of maintained, or stable
> ===
>
> First of all, Avocado and its sub-projects are provided 'AS IS' and
> WITHOUT ANY WARRANTY, as described in the LICENSE file.
>
> The process described here doesn't imply any commitments or
> promises. It's just a set of best practices and recommendations.
>
> When something is identified as "stable" or "maintained", it means the
> development community makes a conscious effort to keep it working and
> consider reports of bugs and issues as high priorities.  Fixes
> submitted for these issues will also be considered high priorities,
> although they will be accepted only if they pass the general
> acceptance criteria for new contributions (design, quality,
> documentation, testing, etc), at the development team discretion.
>
>
> Maintained projects and platforms
> =
>
> The only maintained project as of today is the Avocado Test Runner,
> including its APIs and core plugins (the contents of the main avocado
> git repository).
>
> Other projects kept under the "Avocado Umbrella" in github may be
> maintained by different teams (e.g.: Avocado-VT) or be considered
> experimental (e.g.: avocado-server and avocado-virt).
>
> More about Avocado-VT in its own section further down.
>
> As a general rule, fixes and bug reports for Avocado when running in
> any modern Linux distribution are welcome.
>
> But given the limited capacity of the development team, packaged
> versions of Avocado will be tested and maintained only for the
> following Linux distributions:
>
>  * RHEL 7.x (latest)
>  * Fedora (stable releases from the Fedora projects)
>
> Currently all packages produced by the Avocado projects are "noarch".
> That means that they could be