(more revision) |
(revise for new rawhide/branched approach) |
||
| Line 8: | Line 8: | ||
22 20141208 | 22 20141208 | ||
It can be called with various parameters: {{code|release}}, {{code|date}}, {{code|milestone}}, {{code|compose | It can be called with various parameters: {{code|release}}, {{code|date}}, {{code|milestone}}, {{code|compose}}: | ||
* {{code|<nowiki>{{CurrentFedoraCompose|release}}</nowiki>}} | * {{code|<nowiki>{{CurrentFedoraCompose|release}}</nowiki>}} | ||
| Line 18: | Line 18: | ||
* {{code|<nowiki>{{CurrentFedoraCompose|compose}}</nowiki>}} | * {{code|<nowiki>{{CurrentFedoraCompose|compose}}</nowiki>}} | ||
TC1 | TC1 | ||
If the current nominated compose is a nightly build, {{code|milestone}} and {{code|compose}} output will be empty; if the current nominated compose is a TC/RC, {{code|date}} output will be empty (you can take advantage of this to check which type the current nominated compose is, with the {{code|<nowiki>{{#ifeq:}}</nowiki>}} parser function). The {{code| | If the current nominated compose is a nightly build, {{code|milestone}} will be Branched or Rawhide, and {{code|compose}} output will be empty; if the current nominated compose is a TC/RC, {{code|date}} output will be empty (you can take advantage of this to check which type the current nominated compose is, with the {{code|<nowiki>{{#ifeq:}}</nowiki>}} parser function). The {{code|milestone}} output for nightly composes indicates whether the compose to be tested is from [[Releases/Rawhide|Rawhide]] or [[Releases/Branched|Branched]]. | ||
It can be used in various ways; {{command|relval report-results}} uses it to guess the compose for which the user most likely wants to report results, and the [[Template:Release validation instructions|validation testing instruction template]] uses it to display a note on result pages that are not for the current compose, warning that they are not for the current compose and linking to it, for example. | It can be used in various ways; {{command|relval report-results}} uses it to guess the compose for which the user most likely wants to report results, and the [[Template:Release validation instructions|validation testing instruction template]] uses it to display a note on result pages that are not for the current compose, warning that they are not for the current compose and linking to it, for example. | ||
Revision as of 19:37, 18 December 2014
This template records what is considered to be the 'current' compose nominated for testing by Fedora QA: either a test compose or release candidate, or a Rawhide or Branched nightly compose. It is updated automatically by relval when the compose sub-command is used with the --current option. It can be edited by hand so long as the slightly complex format is kept.
When called with no parameter, the parameter full, or an invalid parameter, it will return the 'full' version of the compose currently nominated for testing - something like 22 Alpha TC1 for a TC/RC, or 22 20141208 for a nightly compose:
- {{CurrentFedoraCompose}}
- {{CurrentFedoraCompose|full}}
- {{CurrentFedoraCompose|foobar}}
22 20141208
It can be called with various parameters: release, date, milestone, compose:
- {{CurrentFedoraCompose|release}}
22
- {{CurrentFedoraCompose|date}}
20141208
- {{CurrentFedoraCompose|milestone}}
Alpha
- {{CurrentFedoraCompose|compose}}
TC1
If the current nominated compose is a nightly build, milestone will be Branched or Rawhide, and compose output will be empty; if the current nominated compose is a TC/RC, date output will be empty (you can take advantage of this to check which type the current nominated compose is, with the {{#ifeq:}} parser function). The milestone output for nightly composes indicates whether the compose to be tested is from Rawhide or Branched.
It can be used in various ways; relval report-results uses it to guess the compose for which the user most likely wants to report results, and the validation testing instruction template uses it to display a note on result pages that are not for the current compose, warning that they are not for the current compose and linking to it, for example.