operations/docs
operations/docs
3
2
Fork 11
Code Issues 3 Pull requests 2 Activity Actions

releases: comply with "one sentence per line" convention

Browse source 
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
This commit is contained in:
Daniel Berrangé 2026-07-15 09:44:12 +01:00 • committed by Aoife Moloney
commit 98ef1c0511
22 changed files with 39 additions and 89 deletions
Download patch file Download diff file Expand all files Collapse all files

7
releases/modules/ROOT/pages/f34/blocking.adoc
View file

@ -2,16 +2,13 @@
:release-version: 34
This is the list of release-blocking deliverables.
The goal is to provide single point of information for Fedora QA,
Release Engineering
and other teams.
The goal is to provide single point of information for Fedora QA, Release Engineering and other teams.
* QA knows what's release blocking and they know where testing priority is
* Release Engineering knows what's going to be produced for upcoming release ahead of time
* We can avoid last minute juggling with release at Go/No-Go meeting
This list is static
and will be updated when a Change proposal that includes changing the blocking status is approved by FESCo.
This list is static and will be updated when a Change proposal that includes changing the blocking status is approved by FESCo.
NOTE: This is not an exhaustive list of Fedora deliverables.
This page only lists the blocking deliverables.

3
releases/modules/ROOT/pages/f34/spins.adoc
View file

@ -3,8 +3,7 @@
This page lists Spins (and Labs) that will be produced for Fedora Linux {release-version}.
NOTE: If the maximum size for a spin needs to be updated,
file an issue against https://pagure.io/fedora-qa/relval/issues[relval].
NOTE: If the maximum size for a spin needs to be updated, file an issue against https://pagure.io/fedora-qa/relval/issues[relval].
[cols="2,5,2"]
.F{release-version} Spins and Labs

7
releases/modules/ROOT/pages/f35/blocking.adoc
View file

@ -2,16 +2,13 @@
:release-version: 35
This is the list of release-blocking deliverables.
The goal is to provide single point of information for Fedora QA,
Release Engineering
and other teams.
The goal is to provide single point of information for Fedora QA, Release Engineering and other teams.
* QA knows what's release blocking and they know where testing priority is
* Release Engineering knows what's going to be produced for upcoming release ahead of time
* We can avoid last minute juggling with release at Go/No-Go meeting
This list is static
and will be updated when a Change proposal that includes changing the blocking status is approved by FESCo.
This list is static and will be updated when a Change proposal that includes changing the blocking status is approved by FESCo.
NOTE: This is not an exhaustive list of Fedora deliverables.
This page only lists the blocking deliverables.

3
releases/modules/ROOT/pages/f35/spins.adoc
View file

@ -3,8 +3,7 @@
This page lists Spins (and Labs) that will be produced for Fedora Linux {release-version}.
NOTE: If the maximum size for a spin needs to be updated,
file an issue against https://pagure.io/fedora-qa/relval/issues[relval].
NOTE: If the maximum size for a spin needs to be updated, file an issue against https://pagure.io/fedora-qa/relval/issues[relval].
[cols="2,5,2"]
.F{release-version} Spins and Labs

7
releases/modules/ROOT/pages/f36/blocking.adoc
View file

@ -2,16 +2,13 @@
:release-version: 36
This is the list of release-blocking deliverables.
The goal is to provide single point of information for Fedora QA,
Release Engineering
and other teams.
The goal is to provide single point of information for Fedora QA, Release Engineering and other teams.
* QA knows what's release blocking and they know where testing priority is
* Release Engineering knows what's going to be produced for upcoming release ahead of time
* We can avoid last minute juggling with release at Go/No-Go meeting
This list is static
and will be updated when a Change proposal that includes changing the blocking status is approved by FESCo.
This list is static and will be updated when a Change proposal that includes changing the blocking status is approved by FESCo.
NOTE: This is not an exhaustive list of Fedora deliverables.
This page only lists the blocking deliverables.

3
releases/modules/ROOT/pages/f36/spins.adoc
View file

@ -3,8 +3,7 @@
This page lists Spins (and Labs) that will be produced for Fedora Linux {release-version}.
NOTE: If the maximum size for a spin needs to be updated,
file an issue against https://pagure.io/fedora-qa/relval/issues[relval].
NOTE: If the maximum size for a spin needs to be updated, file an issue against https://pagure.io/fedora-qa/relval/issues[relval].
[cols="2,5,2"]
.F{release-version} Spins and Labs

7
releases/modules/ROOT/pages/f37/blocking.adoc
View file

@ -2,16 +2,13 @@
:release-version: 37
This is the list of release-blocking deliverables.
The goal is to provide single point of information for Fedora QA,
Release Engineering
and other teams.
The goal is to provide single point of information for Fedora QA, Release Engineering and other teams.
* QA knows what's release blocking and they know where testing priority is
* Release Engineering knows what's going to be produced for upcoming release ahead of time
* We can avoid last minute juggling with release at Go/No-Go meeting
This list is static
and will be updated when a Change proposal that includes changing the blocking status is approved by FESCo.
This list is static and will be updated when a Change proposal that includes changing the blocking status is approved by FESCo.
NOTE: This is not an exhaustive list of Fedora deliverables.
This page only lists the blocking deliverables.

3
releases/modules/ROOT/pages/f37/spins.adoc
View file

@ -3,8 +3,7 @@
This page lists Spins (and Labs) that will be produced for Fedora Linux {release-version}.
NOTE: If the maximum size for a spin needs to be updated,
file an issue against https://pagure.io/fedora-qa/relval/issues[relval].
NOTE: If the maximum size for a spin needs to be updated, file an issue against https://pagure.io/fedora-qa/relval/issues[relval].
[cols="2,5,2"]
.F{release-version} Spins and Labs

7
releases/modules/ROOT/pages/f38/blocking.adoc
View file

@ -2,16 +2,13 @@
:release-version: 38
This is the list of release-blocking deliverables.
The goal is to provide single point of information for Fedora QA,
Release Engineering
and other teams.
The goal is to provide single point of information for Fedora QA, Release Engineering and other teams.
* QA knows what's release blocking and they know where testing priority is
* Release Engineering knows what's going to be produced for upcoming release ahead of time
* We can avoid last minute juggling with release at Go/No-Go meeting
This list is static
and will be updated when a Change proposal that includes changing the blocking status is approved by FESCo.
This list is static and will be updated when a Change proposal that includes changing the blocking status is approved by FESCo.
NOTE: This is not an exhaustive list of Fedora deliverables.
This page only lists the blocking deliverables.

3
releases/modules/ROOT/pages/f38/spins.adoc
View file

@ -3,8 +3,7 @@
This page lists Spins (and Labs) that will be produced for Fedora Linux {release-version}.
NOTE: If the maximum size for a spin needs to be updated,
file an issue against https://pagure.io/fedora-qa/relval/issues[relval].
NOTE: If the maximum size for a spin needs to be updated, file an issue against https://pagure.io/fedora-qa/relval/issues[relval].
[cols="2,5,2"]
.F{release-version} Spins and Labs

10
releases/modules/ROOT/pages/f39/blocking.adoc
View file

@ -2,16 +2,13 @@
:release-version: 39
This is the list of release-blocking deliverables.
The goal is to provide single point of information for Fedora QA,
Release Engineering
and other teams.
The goal is to provide single point of information for Fedora QA, Release Engineering and other teams.
* QA knows what's release blocking and they know where testing priority is
* Release Engineering knows what's going to be produced for upcoming release ahead of time
* We can avoid last minute juggling with release at Go/No-Go meeting
This list is static
and will be updated when a Change proposal that includes changing the blocking status is approved by FESCo.
This list is static and will be updated when a Change proposal that includes changing the blocking status is approved by FESCo.
NOTE: This is not an exhaustive list of Fedora deliverables.
This page only lists the blocking deliverables.
@ -19,8 +16,7 @@ Teams are encouraged to maintain a list of non-blocking deliverables for which t
NOTE: Fedora CoreOS deliverables are not included here because they use a different compose process.
NOTE: Images starting "IoT/" below are found in the separate Fedora-IoT composes, not the main
Fedora composes.
NOTE: Images starting "IoT/" below are found in the separate Fedora-IoT composes, not the main Fedora composes.
[cols="7,1,1"]
.F{release-version} Release-Blocking Deliverables

3
releases/modules/ROOT/pages/f39/spins.adoc
View file

@ -3,8 +3,7 @@
This page lists Spins (and Labs) that will be produced for Fedora Linux {release-version}.
NOTE: If the maximum size for a spin needs to be updated,
file an issue against https://pagure.io/fedora-qa/relval/issues[relval].
NOTE: If the maximum size for a spin needs to be updated, file an issue against https://pagure.io/fedora-qa/relval/issues[relval].
[cols="2,5,2"]
.F{release-version} Spins and Labs

10
releases/modules/ROOT/pages/f40/blocking.adoc
View file

@ -2,16 +2,13 @@
:release-version: 40
This is the list of release-blocking deliverables.
The goal is to provide single point of information for Fedora QA,
Release Engineering
and other teams.
The goal is to provide single point of information for Fedora QA, Release Engineering and other teams.
* QA knows what's release blocking and they know where testing priority is
* Release Engineering knows what's going to be produced for upcoming release ahead of time
* We can avoid last minute juggling with release at Go/No-Go meeting
This list is static
and will be updated when a Change proposal that includes changing the blocking status is approved by FESCo.
This list is static and will be updated when a Change proposal that includes changing the blocking status is approved by FESCo.
NOTE: This is not an exhaustive list of Fedora deliverables.
This page only lists the blocking deliverables.
@ -19,8 +16,7 @@ Teams are encouraged to maintain a list of non-blocking deliverables for which t
NOTE: Fedora CoreOS deliverables are not included here because they use a different compose process.
NOTE: Images starting "IoT/" below are found in the separate Fedora-IoT composes, not the main
Fedora composes.
NOTE: Images starting "IoT/" below are found in the separate Fedora-IoT composes, not the main Fedora composes.
NOTE: Maximum sizes for compressed raw disk images apply to the uncompressed size.

3
releases/modules/ROOT/pages/f40/spins.adoc
View file

@ -3,8 +3,7 @@
This page lists Spins (and Labs) that will be produced for Fedora Linux {release-version}.
NOTE: If the maximum size for a spin needs to be updated,
file an issue against https://pagure.io/fedora-qa/relval/issues[relval].
NOTE: If the maximum size for a spin needs to be updated, file an issue against https://pagure.io/fedora-qa/relval/issues[relval].
[cols="2,5,2"]
.F{release-version} Spins and Labs

10
releases/modules/ROOT/pages/f41/blocking.adoc
View file

@ -2,16 +2,13 @@
:release-version: 41
This is the list of release-blocking deliverables.
The goal is to provide single point of information for Fedora QA,
Release Engineering
and other teams.
The goal is to provide single point of information for Fedora QA, Release Engineering and other teams.
* QA knows what's release blocking and they know where testing priority is
* Release Engineering knows what's going to be produced for upcoming release ahead of time
* We can avoid last minute juggling with release at Go/No-Go meeting
This list is static
and will be updated when a Change proposal that includes changing the blocking status is approved by FESCo.
This list is static and will be updated when a Change proposal that includes changing the blocking status is approved by FESCo.
NOTE: This is not an exhaustive list of Fedora deliverables.
This page only lists the blocking deliverables.
@ -19,8 +16,7 @@ Teams are encouraged to maintain a list of non-blocking deliverables for which t
NOTE: Fedora CoreOS deliverables are not included here because they use a different compose process.
NOTE: Images starting "IoT/" below are found in the separate Fedora-IoT composes, not the main
Fedora composes.
NOTE: Images starting "IoT/" below are found in the separate Fedora-IoT composes, not the main Fedora composes.
NOTE: Maximum sizes for compressed raw disk images apply to the uncompressed size.

3
releases/modules/ROOT/pages/f41/spins.adoc
View file

@ -3,8 +3,7 @@
This page lists Spins (and Labs) that will be produced for Fedora Linux {release-version}.
NOTE: If the maximum size for a spin needs to be updated,
file an issue against https://pagure.io/fedora-qa/relval/issues[relval].
NOTE: If the maximum size for a spin needs to be updated, file an issue against https://pagure.io/fedora-qa/relval/issues[relval].
[cols="2,5,2"]
.F{release-version} Spins and Labs

10
releases/modules/ROOT/pages/f42/blocking.adoc
View file

@ -2,16 +2,13 @@
:release-version: 42
This is the list of release-blocking deliverables.
The goal is to provide single point of information for Fedora QA,
Release Engineering
and other teams.
The goal is to provide single point of information for Fedora QA, Release Engineering and other teams.
* QA knows what's release blocking and they know where testing priority is
* Release Engineering knows what's going to be produced for upcoming release ahead of time
* We can avoid last minute juggling with release at Go/No-Go meeting
This list is static
and will be updated when a Change proposal that includes changing the blocking status is approved by FESCo.
This list is static and will be updated when a Change proposal that includes changing the blocking status is approved by FESCo.
NOTE: This is not an exhaustive list of Fedora deliverables.
This page only lists the blocking deliverables.
@ -19,8 +16,7 @@ Teams are encouraged to maintain a list of non-blocking deliverables for which t
NOTE: Fedora CoreOS deliverables are not included here because they use a different compose process.
NOTE: Images starting "IoT/" below are found in the separate Fedora-IoT composes, not the main
Fedora composes.
NOTE: Images starting "IoT/" below are found in the separate Fedora-IoT composes, not the main Fedora composes.
NOTE: Maximum sizes for compressed raw disk images apply to the uncompressed size.

3
releases/modules/ROOT/pages/f42/spins.adoc
View file

@ -3,8 +3,7 @@
This page lists Spins (and Labs) that will be produced for Fedora Linux {release-version}.
NOTE: If the maximum size for a spin needs to be updated,
file an issue against https://pagure.io/fedora-qa/relval/issues[relval].
NOTE: If the maximum size for a spin needs to be updated, file an issue against https://pagure.io/fedora-qa/relval/issues[relval].
[cols="2,5,2"]
.F{release-version} Spins and Labs

10
releases/modules/ROOT/pages/f43/blocking.adoc
View file

@ -2,16 +2,13 @@
:release-version: 43
This is the list of release-blocking deliverables.
The goal is to provide single point of information for Fedora QA,
Release Engineering
and other teams.
The goal is to provide single point of information for Fedora QA, Release Engineering and other teams.
* QA knows what's release blocking and they know where testing priority is
* Release Engineering knows what's going to be produced for upcoming release ahead of time
* We can avoid last minute juggling with release at Go/No-Go meeting
This list is static
and will be updated when a Change proposal that includes changing the blocking status is approved by FESCo.
This list is static and will be updated when a Change proposal that includes changing the blocking status is approved by FESCo.
NOTE: This is not an exhaustive list of Fedora deliverables.
This page only lists the blocking deliverables.
@ -19,8 +16,7 @@ Teams are encouraged to maintain a list of non-blocking deliverables for which t
NOTE: Fedora CoreOS deliverables are not included here because they use a different compose process.
NOTE: Images starting "IoT/" below are found in the separate Fedora-IoT composes, not the main
Fedora composes.
NOTE: Images starting "IoT/" below are found in the separate Fedora-IoT composes, not the main Fedora composes.
NOTE: Maximum sizes for compressed raw disk images apply to the uncompressed size.

3
releases/modules/ROOT/pages/f43/spins.adoc
View file

@ -3,8 +3,7 @@
This page lists Spins (and Labs) that will be produced for Fedora Linux {release-version}.
NOTE: If the maximum size for a spin needs to be updated,
file an issue against https://pagure.io/fedora-qa/relval/issues[relval].
NOTE: If the maximum size for a spin needs to be updated, file an issue against https://pagure.io/fedora-qa/relval/issues[relval].
[cols="2,5,2"]
.F{release-version} Spins and Labs

10
releases/modules/ROOT/pages/f44/blocking.adoc
View file

@ -2,16 +2,13 @@
:release-version: 44
This is the list of release-blocking deliverables.
The goal is to provide single point of information for Fedora QA,
Release Engineering
and other teams.
The goal is to provide single point of information for Fedora QA, Release Engineering and other teams.
* QA knows what's release blocking and they know where testing priority is
* Release Engineering knows what's going to be produced for upcoming release ahead of time
* We can avoid last minute juggling with release at Go/No-Go meeting
This list is static
and will be updated when a Change proposal that includes changing the blocking status is approved by FESCo.
This list is static and will be updated when a Change proposal that includes changing the blocking status is approved by FESCo.
NOTE: This is not an exhaustive list of Fedora deliverables.
This page only lists the blocking deliverables.
@ -19,8 +16,7 @@ Teams are encouraged to maintain a list of non-blocking deliverables for which t
NOTE: Fedora CoreOS deliverables are not included here because they use a different compose process.
NOTE: Images starting "IoT/" below are found in the separate Fedora-IoT composes, not the main
Fedora composes.
NOTE: Images starting "IoT/" below are found in the separate Fedora-IoT composes, not the main Fedora composes.
NOTE: Maximum sizes for compressed raw disk images apply to the uncompressed size.

3
releases/modules/ROOT/pages/f44/spins.adoc
View file

@ -3,8 +3,7 @@
This page lists Spins (and Labs) that will be produced for Fedora Linux {release-version}.
NOTE: If the maximum size for a spin needs to be updated,
file an issue against https://pagure.io/fedora-qa/relval/issues[relval].
NOTE: If the maximum size for a spin needs to be updated, file an issue against https://pagure.io/fedora-qa/relval/issues[relval].
[cols="2,5,2"]
.F{release-version} Spins and Labs