GeezerVison is showing github.com — fixing aliases · validatedpatterns/docs@5e41688
File treeExpand file treeCollapse file tree Open diff view settings Expand file treeCollapse file tree Open diff view settings Collapse file Copy file name to clipboardExpand all lines: content/contribute/implementation.adoc +1Lines changed: 1 addition & 0 deletions - Display the source diff
- Display the rich diff
| Original file line number | Diff line number | Diff line change |
|---|
| 4 | 4 | parent: Validated Pattern tiers | 5 | 5 | title: Implementation requirements | 6 | 6 | weight: 42 | | 7 | +aliases: /learn/implementation/ | 7 | 8 | aliases: /requirements/implementation/ | 8 | 9 | --- | 9 | 10 |
| |
Collapse file Copy file name to clipboardExpand all lines: content/contribute/maintained.adoc +3-3Lines changed: 3 additions & 3 deletions - Display the source diff
- Display the rich diff
| Original file line number | Diff line number | Diff line change |
|---|
| 4 | 4 | parent: Validated Pattern tiers | 5 | 5 | title: Validated Patterns - Maintained tier | 6 | 6 | weight: 45 | 7 | | -aliases: /requirements/maintained/ | | 7 | +aliases: /requirements/validated/ | 8 | 8 | --- | 9 | 9 |
| 10 | 10 | :toc: | @@ -29,14 +29,14 @@ Each {maintained} pattern represents an ongoing maintenance, support, and testin | 29 | 29 |
| 30 | 30 | 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. | 31 | 31 |
| 32 | | -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. | | 32 | +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. | 33 | 33 |
| 34 | 34 |
| 35 | 35 | [id="requirements-maintained-tier"] | 36 | 36 | == Requirements for the {maintained} tier | 37 | 37 |
| 38 | 38 | The {maintained} patterns have deliverable and requirements in addition to those | 39 | | -specified for the link:/requirements/tested/[Tested tier]. | | 39 | +specified for the link:/contribute/tested[Tested tier]. | 40 | 40 |
| 41 | 41 | The requirements are categorized as follows: | 42 | 42 |
| |
Collapse file Copy file name to clipboardExpand all lines: content/contribute/sandbox.adoc +2-3Lines changed: 2 additions & 3 deletions - Display the source diff
- Display the rich diff
| Original file line number | Diff line number | Diff line change |
|---|
| 5 | 5 | title: Validated Patterns - Sandbox tier | 6 | 6 | weight: 43 | 7 | 7 | aliases: /requirements/community/ | 8 | | -aliases: /requirements/sandbox/ | 9 | 8 | --- | 10 | 9 |
| 11 | 10 | :toc: | @@ -48,7 +47,7 @@ These are optional or desirable features, but their absence does not hinder the | 48 | 47 | === Must | 49 | 48 | A {sandbox} pattern must continue to meet the following criteria to remain in the {sandbox} tier: | 50 | 49 |
| 51 | | -* A {sandbox} pattern must conform to the common technical link:/requirements/implementation/[implementation requirements]. | | 50 | +* A {sandbox} pattern must conform to the common technical link:/contribute/implementation/[implementation requirements]. | 52 | 51 | * A {sandbox} pattern must be able to be deployed onto a freshly deployed OpenShift cluster without prior modification or tuning. | 53 | 52 | * A {sandbox} pattern must include a top-level README file that highlights the business problem and how the pattern solves it. | 54 | 53 | * A {sandbox} pattern must include an architecture drawing. The specific tool or format is flexible as long as the meaning is clear. | @@ -69,4 +68,4 @@ The {solution-name-upstream} team commits to maintaining the framework, but will | 69 | 68 |
| 70 | 69 | * 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. | 71 | 70 | * A {sandbox} pattern can be listed on the link:https://validatedpatterns.io[https://validatedpatterns.io] site. | 72 | | -* A {sandbox} pattern meeting additional criteria can be nominated for promotion to the link:/learn/tested/[Tested tier]. | | 71 | +* A {sandbox} pattern meeting additional criteria can be nominated for promotion to the link:/contribute/tested/[Tested tier]. |
Collapse file Copy file name to clipboardExpand all lines: content/contribute/test-artefacts.adoc -1Lines changed: 0 additions & 1 deletion - Display the source diff
- Display the rich diff
| Original file line number | Diff line number | Diff line change |
|---|
| 4 | 4 | parent: Validated Pattern tiers | 5 | 5 | title: Testing Artefacts | 6 | 6 | weight: 50 | 7 | | -aliases: /requirements/tested/ | 8 | 7 | --- | 9 | 8 |
| 10 | 9 | :toc: | |
Collapse file Copy file name to clipboardExpand all lines: content/contribute/tested.adoc +3-4Lines changed: 3 additions & 4 deletions - Display the source diff
- Display the rich diff
| Original file line number | Diff line number | Diff line change |
|---|
| 4 | 4 | parent: Validated Pattern tiers | 5 | 5 | title: Validated Patterns - Tested tier | 6 | 6 | weight: 44 | 7 | | -aliases: /requirements/tested/ | 8 | 7 | --- | 9 | 8 |
| 10 | 9 | :toc: | @@ -18,7 +17,7 @@ include::modules/comm-attributes.adoc[] | 18 | 17 | 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). | 19 | 18 |
| 20 | 19 | [id="nominating-a-pattern-for-tested-tier"] | 21 | | -== Nominating a a pattern for the {tested} tier | | 20 | +== Nominating a pattern for the {tested} tier | 22 | 21 |
| 23 | 22 | | 24 | 23 |
| @@ -35,7 +34,7 @@ In limited cases, the {solution-name-upstream} team may consider taking on that | 35 | 34 | [id="requirements-tested-tier"] | 36 | 35 | == Requirements for the {tested} tier | 37 | 36 |
| 38 | | -A {tested} patterns have deliverable and requirements in addition to those specified for the link:/requirements/sandbox/[Sandbox tier]. | | 37 | +A {tested} patterns have deliverable and requirements in addition to those specified for the link:/contribute/sandbox/[Sandbox tier]. | 39 | 38 |
| 40 | 39 | The requirements are categorized as follows: | 41 | 40 |
| @@ -67,7 +66,7 @@ Example: https://docs.google.com/document/d/12KQhdzjVIsxRURTnWAckiEMB3_96oWBjtlT | 67 | 66 |
| 68 | 67 | * A {tested} pattern must nominate at least one currently supported {rh-ocp} release to test against. | 69 | 68 | * A {tested} pattern must ensure the test plan passes at least once per quarter. | 70 | | -* 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]. | | 69 | +* 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]. | 71 | 70 |
| 72 | 71 | [NOTE] | 73 | 72 | ==== | |
|