Exceptionally, this wiki is under maintenance.

You can continue to browse it to discover the STM32MP1 series and associated ecosystems (STM32 boards, embedded software, development tools, trace & debug tools...) but contributors can not improve their favorite articles, during phase.

Thank you for your understanding.

Revision

< Template:EcosystemRelease
Revision as of 12:53, 14 June 2023 by Registered User
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

1 Usage

The EcosystemRelease/Revision template returns the status for an ecosystem release revision in the flow associated with this wiki (e.g. v1.y.z ,or v2.y.z, or...), or the revision (x.y.z) of the latest ecosystem release.

Usage: {{EcosystemRelease/Revision | revision=<revision>}}

Where:

  • <revision> is the mandatory revision of the ecosystem release for which a status is requested. The possible values are:
    • latest to get the revision (x.y.z) of the latest major ecosystem release.
    • 5.0.0 (June 2023 major ecosystem release revision).
    • 4.1.0 (November 2022 major ecosystem release revision): possible but not recommended.
    • 4.0.2 (July 2022 minor ecosystem release revision): possible but not recommended.
    • 4.0.0 (June 2022 major ecosystem release revision): possible but not recommended.
    • 3.1.0 (November 2021 major ecosystem release revision): possible but not recommended.
    • 3.0.0 (March 2021 major ecosystem release revision): possible but not recommended.
    • 2.1.0 (November 2020 major ecosystem release revision) : possible but not recommended.
    • 2.0.0 (June 2020 major ecosystem release revision) : possible but not recommended.
    • x.0.0, x.1.0, x.2.0 and 0.y.0 values are reserved to the examples and the helper files.

The returned value is:

  • x.y.z (revision of the latest ecosystem release), if <revision> is set to latest.
  • latest, if <revision> is the latest one, in the flow associated with this wiki.
  • legacy, if <revision> is a legacy one, in the flow associated with this wiki.
  • next, if <revision> is a planned one, in the flow associated with this wiki.
  • former, if <revision> is part of a former flow that is not the one associated with this wiki.
  • unknown, if <revision> is not supported.

E.g.,

  • At 3.1.0 deployment : next: none, legacy: 3.0.0, latest: 3.1.0, former: 1.x.y, 2.x.y
  • During 3.1.0 preparation: next: 3.1.0, legacy: none, latest: 3.0.0, former: 1.x.y, 2.x.y.
  • 3.0.0 deployed (initial situation): next: none, legacy: none, latest: 3.0.0, former: 1.x.y, 2.x.y.

2 Basic examples

You type You get
v5.0.0 revision (latest)
{{EcosystemRelease/Revision | revision=5.0.0}}

latest

Latest revision
{{EcosystemRelease/Revision | revision=latest}}

5.0.0

Former revisions
{{EcosystemRelease/Revision | revision=4.1.0}}<br />
{{EcosystemRelease/Revision | revision=4.0.2}}<br />
{{EcosystemRelease/Revision | revision=4.0.0}}<br />
{{EcosystemRelease/Revision | revision=3.1.0}}<br />
{{EcosystemRelease/Revision | revision=3.0.0}}<br />
{{EcosystemRelease/Revision | revision=2.1.0}}<br />
{{EcosystemRelease/Revision | revision=2.0.0}}<br />
{{EcosystemRelease/Revision | revision=1.2.0}}<br />
{{EcosystemRelease/Revision | revision=1.1.0}}<br />
{{EcosystemRelease/Revision | revision=1.0.0}}

former
former
former
former
former
former
former
former
former
former

3 More examples

You type You get
vx.0.0 revision (legacy)
{{EcosystemRelease/Revision | revision=x.0.0}}

legacy

vx.1.0 revision (latest)
{{EcosystemRelease/Revision | revision=x.1.0}}

latest

vx.2.0 revision (next)
{{EcosystemRelease/Revision | revision=x.2.0}}

next

v0.y.0 revision (former)
{{EcosystemRelease/Revision | revision=0.y.0}}

former

Unknown revision
{{EcosystemRelease/Revision | revision=10.20.30}}

unknown

Unspecified revision
{{EcosystemRelease/Revision}}

unknown

4 Code

unknown