Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify threshold for Tier 2 platforms. #192

Merged
merged 6 commits into from May 21, 2019

Conversation

Projects
None yet
4 participants
@tfoote
Copy link
Member

commented May 10, 2019

Add clarity to Tier 2 thresholds and help define the support tiers better.

Clarify threshold for Tier 2 platforms.
Add clarity to Tier 2 thresholds and help define the support tiers better.
Show resolved Hide resolved rep-2000.rst Outdated
Show resolved Hide resolved rep-2000.rst Outdated
Show resolved Hide resolved rep-2000.rst Outdated
@thomas-moulard
Copy link

left a comment

Thanks a lot Tully - I asked for more clarification to ensure we stay aligned. If you don't want to set rules in stone, maybe giving out a few examples could help?

Something like:

For a TSC member to support a Tier 2 platform, they should:

* Implement:
** Nightly CI for ci.ros2.org
** Nightly packaging job for ci.ros2.org
* Monitor continuously:
** CI and packaging job should stay green or be fixed in less than N days
** Bugs reported for this platform should be triaged in less than X days and fixed in less than Y days.
etc.
* Commit to spend X engineering-hours before each release for QA

If X, Y or Z is not done, then the platform would be downgraded from Tier2 to Tier3 for the next release.
Show resolved Hide resolved rep-2000.rst Outdated
Show resolved Hide resolved rep-2000.rst Outdated
Show resolved Hide resolved rep-2000.rst Outdated
Tier 2 platforms may have downloadable binary archives.
Errors may be present in released product versions for Tier 2 platforms.
Known errors in Tier 2 platforms will be addressed subject to resource availability on a best effort basis and may or may not be corrected prior to new version releases.
One or more entities should be committed to continuing support of the platform.

This comment has been minimized.

Copy link
@thomas-moulard

thomas-moulard May 10, 2019

What means support in this context? Is this keeping the CI green?

@dirk-thomas

This comment has been minimized.

Copy link
Member

commented May 10, 2019

** CI and packaging job should stay green or be fixed in less than N days
** Bugs reported for this platform should be triaged in less than X days and fixed in less than Y days.
etc.

These kind of guarantees aren't really compatible with the other existing statement:

Known errors in Tier 2 platforms will be addressed subject to resource availability on a best effort basis and may or may not be corrected prior to new version releases.

The difficulty here is to ensure that someone takes care about a tier 2 platform but doesn't imply a tier 1 support level.

Show resolved Hide resolved rep-2000.rst Outdated
@thomas-moulard
Copy link

left a comment

Thanks Tully, this is already clearer. We can continue the ARM H/F discussion offline if we need more info on our side.

@@ -179,6 +179,10 @@ Crystal Clemmys (December 2018 - December 2019)

Support Tiers:

Platforms are defined as a combination of the OS, the Architecture, and the RMW implementation.
By default the tiers are expected to apply upto the desktop variant in a rosdistro, unless otherwise specified.

This comment has been minimized.

Copy link
@dirk-thomas

dirk-thomas May 14, 2019

Member

One more nitpick: "rosdistro" seems weird here. I would suggest "ROS distribution" instead.

@@ -179,6 +179,10 @@ Crystal Clemmys (December 2018 - December 2019)

Support Tiers:

Platforms are defined as a combination of the OS, the Architecture, and the RMW implementation.
By default the tiers are expected to apply upto the desktop variant in a rosdistro, unless otherwise specified.

This comment has been minimized.

Copy link
@chapulina

chapulina May 17, 2019

Nit:

  • Architecture could be lower case
  • upto -> up to

@tfoote tfoote merged commit f4b4c7e into master May 21, 2019

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details

@tfoote tfoote deleted the tfoote-tier-2 branch May 21, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.