|A pattern categorized under the {sandbox} tier provides you with an entry point to onboard to {solution-name-upstream}. The minimum requirement to qualify for the {sandbox} tier is to start with the patterns framework and include minimal documentation.
The patterns in this tier might be in a work-in-progress state; and they might have been manually tested on a limited set of platforms.
|link:/requirements/tested/[{tested-tier-first}]
|link:/contribute/tested[{tested-tier-first}]
|A pattern categorized under the {tested} tier implies that the pattern might have been recently working on at least one recent version of {rh-ocp}. Qualifying for this tier might require additional work for the pattern’s owner, who might be a partner or a motivated subject matter expert (SME).
The patterns in this tier might have a defined business problem with a demonstration. The patterns might have a manual or automated test plan, which passes at least once for each new {rh-ocp} minor version.
|A pattern categorized under the {maintained} tier implies that the pattern might have been functional on all currently supported extended update support (EUS) versions of {rh-ocp}. Qualifying for this tier might require additional work for the pattern’s owner who might be a partner or a motivated SME.
The patterns in this tier might have a formal release process with patch releases. They might have continuous integration (CI) automation testing.
@@ -29,14 +29,14 @@ Each {maintained} pattern represents an ongoing maintenance, support, and testin
For this reason we have designed the tiers and our processes to facilitate this to occur outside of the team by any sufficiently motivated party, including other parts of Red Hat, partners, and even customers.
In limited cases, the {solution-name-upstream} team may consider taking on that work, however, it is recommended that you contact the team at least 4 weeks prior to the end of a given quarter for the necessary work to be considered as part of the following quarter's planning process.
In limited cases, the {solution-name-upstream} team may consider taking on that work, however, it is recommended that you contact the team at least 4 weeks before the end of a given quarter for the necessary work to be considered as part of the following quarter's planning process.
[id="requirements-maintained-tier"]
== Requirements for the {maintained} tier
The {maintained} patterns have deliverable and requirements in addition to those
specified for the link:/requirements/tested/[Tested tier].
specified for the link:/contribute/tested[Tested tier].
@@ -48,7 +47,7 @@ These are optional or desirable features, but their absence does not hinder the
=== Must
A {sandbox} pattern must continue to meet the following criteria to remain in the {sandbox} tier:
* A {sandbox} pattern must conform to the common technical link:/requirements/implementation/[implementation requirements].
* A {sandbox} pattern must conform to the common technical link:/contribute/implementation/[implementation requirements].
* A {sandbox} pattern must be able to be deployed onto a freshly deployed OpenShift cluster without prior modification or tuning.
* A {sandbox} pattern must include a top-level README file that highlights the business problem and how the pattern solves it.
* A {sandbox} pattern must include an architecture drawing. The specific tool or format is flexible as long as the meaning is clear.
Expand All
@@ -69,4 +68,4 @@ The {solution-name-upstream} team commits to maintaining the framework, but will
* A {sandbox} pattern (including works-in-progress) can be hosted in the link:https://github.com/validatedpatterns-sandbox[https://github.com/validatedpatterns-sandbox] GitHub organization.
* A {sandbox} pattern can be listed on the link:https://validatedpatterns.io[https://validatedpatterns.io] site.
* A {sandbox} pattern meeting additional criteria can be nominated for promotion to the link:/learn/tested/[Tested tier].
* A {sandbox} pattern meeting additional criteria can be nominated for promotion to the link:/contribute/tested/[Tested tier].
The {tested} tier provides you with additional collateral and reassurance that the pattern was known to be recently working on at least one recent version of {rh-ocp}. Inclusion in this tier requires some additional work for the pattern's owner, which might be a partner or a sufficiently motivated subject matter expert (SME).
[id="nominating-a-pattern-for-tested-tier"]
== Nominating a a pattern for the {tested} tier
== Nominating a pattern for the {tested} tier
If your pattern qualifies or meets the criteria for {tested} tier, submit your nomination to mailto:[email protected][[email protected]].
Expand All
@@ -35,7 +34,7 @@ In limited cases, the {solution-name-upstream} team may consider taking on that
[id="requirements-tested-tier"]
== Requirements for the {tested} tier
A {tested} patterns have deliverable and requirements in addition to those specified for the link:/requirements/sandbox/[Sandbox tier].
A {tested} patterns have deliverable and requirements in addition to those specified for the link:/contribute/sandbox/[Sandbox tier].
* A {tested} pattern must nominate at least one currently supported {rh-ocp} release to test against.
* A {tested} pattern must ensure the test plan passes at least once per quarter.
* A {tested} pattern must create a publicly available JSON file (for example, in an AWS bucket) that records the result of the latest test for each combination of pattern, platform, and {rh-ocp} version. See link:/learn/test-artefacts/[testing artefacts].
* A {tested} pattern must create a publicly available JSON file (for example, in an AWS bucket) that records the result of the latest test for each combination of pattern, platform, and {rh-ocp} version. See link:/contribute/test-artefacts/[testing artefacts].
[NOTE]
====
Expand Down
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402520 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.