#10951 end-of-life template: Explicitly mention no more security announcements
Merged a year ago by kevin. Opened 2 years ago by manfredcolorfu.
manfredcolorfu/releng main  into  main

@@ -1,29 +1,29 @@ 

  Hi all,

  

- Per the Fedora f37 schedule[1] we have started a mass rebuild

- on 2022-07-20 for Fedora f37. We are running this mass rebuild

+ Per the Fedora Linux fN schedule [1] we have started a mass rebuild

+ on YYYY-MM-DD for Fedora fN. We are running this mass rebuild

  for the changes listed in:

  

  https://pagure.io/releng/issues?status=Open&tags=mass+rebuild

  

- This mass rebuild will be done in a side tag (f37-rebuild) and merged

+ This mass rebuild will be done in a side tag (fN-rebuild) and merged

  when completed.

  

  Failures can be seen

- https://kojipkgs.fedoraproject.org/mass-rebuild/f37-failures.html

- <https://kojipkgs.fedoraproject.org/mass-rebuild/f37-failures.html>

+ https://kojipkgs.fedoraproject.org/mass-rebuild/fN-failures.html

+ <https://kojipkgs.fedoraproject.org/mass-rebuild/fN-failures.html>

  

  Things still needing rebuilding

- https://kojipkgs.fedoraproject.org/mass-rebuild/f37-need-rebuild.html

- <https://kojipkgs.fedoraproject.org/mass-rebuild/f37-need-rebuild.html>

+ https://kojipkgs.fedoraproject.org/mass-rebuild/fN-need-rebuild.html

+ <https://kojipkgs.fedoraproject.org/mass-rebuild/fN-need-rebuild.html>

  

  FTBFS (Fails To Build From Source) bugs will be filed shortly after

  the mass rebuild is complete.

  

  Please be sure to let releng know if you see any bugs in the

- reporting. You can contact releng in #fedora-releng channel on Libera.Chat, 

- the #releng:fedoraproject.org room on Matrix, or by dropping an email

- to our list[2] or filing an issue in pagure[3].

+ reporting. You can contact releng in #fedora-releng channel on

+ Libera.Chat, the #releng:fedoraproject.org room on Matrix, or by

+ dropping an email to our list [2] or filing an issue in pagure [3].

  

  This email template is also in https://pagure.io/releng if you wish to

  propose improvements or changes to it.
@@ -32,6 +32,6 @@ 

  

  Fedora Release Engineering

  

- [1] https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html

+ [1] https://fedorapeople.org/groups/schedule/f-fN/f-fN-key-tasks.html

  [2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/

  [3] https://pagure.io/releng/

@@ -1,7 +1,8 @@ 

  Hi all,

  

- Per the Fedora N schedule[1] we started a mass rebuild for Fedora

- N on MMM DD, YYYY. We did a mass rebuild for Fedora N for:

+ Per the Fedora Linux fN schedule [1] we started a mass rebuild for

+ Fedora Linux fN on YYYY-MM-DD. We did a mass rebuild for Fedora

+ Linux fN for:

  

  <list changes that need mass rebuild here>

  https://fedoraproject.org/wiki/Changes/NAME
@@ -16,13 +17,13 @@ 

  builds that need to be addressed by the package maintainers. FTBFS bugs

  will be filed shortly. Please be sure to let releng know if you see any

  bugs in the reporting. You can contact releng in #fedora-releng on

- libera.chat, by dropping an email to our list[2], joining 

- #releng:fedoraproject.org on Matrix, or filing an issue in pagure[3] 

+ libera.chat, by dropping an email to our list [2], joining 

+ #releng:fedoraproject.org on Matrix, or filing an issue in pagure [3] 

  

  Regards,

  Fedora Release Engineering

  

- [1] https://fedorapeople.org/groups/schedule/f-N/f-N-key-tasks.html

+ [1] https://fedorapeople.org/groups/schedule/f-fN/f-fN-key-tasks.html

  [2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/

  [3] https://pagure.io/releng/

  

@@ -1,25 +1,25 @@ 

  Hi All,

  

- Fedora N has now been branched, please be sure to do a git pull

+ Fedora Linux fN has now been branched, please be sure to do a git pull

  --rebase to pick up the new branch, as an additional reminder

  rawhide/fN has been completely isolated from previous releases, so

  this means that anything you do for fN you also have to do in the

- rawhide branch and do a build there. There will be a Fedora N compose

- and it'll appear in

- http://dl.fedoraproject.org/pub/fedora/linux/development/N/ once

+ rawhide branch and do a build there. There will be a Fedora Linux fN

+ compose and it'll appear in

+ http://dl.fedoraproject.org/pub/fedora/linux/development/fN/ once

  complete.

  

  Bodhi is currently enabled in the fN branch like it is for rawhide,

  with automatic update creation. At the hit Beta change freeze point

- in the Fedora N schedule[1] updates-testing will be enabled and

+ in the Fedora Linux fN schedule [1] updates-testing will be enabled and

  manual bodhi updates will be required as in all stable releases.

  

  Two things to remember:

  

  1. The modules will be built for a new platform:fN+1

- 2. FN/branched release is frozen right now until we get a successful

+ 2. fN/branched release is frozen right now until we get a successful

  compose, expect that your fN builds won't be available immediately.

  

  Thanks for understanding.

  

- [1] https://fedorapeople.org/groups/schedule/f-N/f-N-key-tasks.html

+ [1] https://fedorapeople.org/groups/schedule/f-fN/f-fN-key-tasks.html

@@ -1,33 +1,33 @@ 

  Hi all,

  

- Today's an important day on the Fedora N schedule[1], with several

- significant cut-offs. First of all, today is the Bodhi updates-testing

- activation point [2]. That means that from now all Fedora N packages must

- be submitted to updates-testing and pass the relevant

- requirements[3] before they will be marked as 'stable' and moved to

- the fedora repository.

+ Today's an important day on the Fedora Linux fN schedule [1], with

+ several significant cut-offs. First of all, today is the Bodhi

+ updates-testing activation point [2]. That means that from now all

+ Fedora Linux fN packages must be submitted to updates-testing and pass

+ the relevant requirements [3] before they will be marked as 'stable' and

+ moved to the Fedora Repository.

  

- Today is also the Beta freeze[4]. This means that only packages which

- fix accepted blocker or freeze exception bugs[5][6] will be marked as

+ Today is also the Beta freeze [4]. This means that only packages which

+ fix accepted blocker or freeze exception bugs [5][6] will be marked as

  'stable' and included in the Beta composes. Other builds will remain

  in updates-testing until the Beta release is approved, at which point

  the Beta freeze is lifted and packages can move to 'stable' as usual

  until the Final freeze.

  

- Today is also the Software String freeze[7], which means that strings

+ Today is also the Software String freeze [7], which means that strings

  marked for translation in Fedora-translated projects should not now be

- changed for Fedora N.

+ changed for Fedora Linux fN.

  

- Finally, today is the 'completion deadline' Change Checkpoint[8],

- meaning that Fedora N Changes must now be 'feature complete or close

- enough to completion that a majority of its functionality can be

+ Finally, today is the 'completion deadline' Change Checkpoint [8],

+ meaning that Fedora Linux fN Changes must now be 'feature complete or

+ close enough to completion that a majority of its functionality can be

  tested'. All tracking bugs should be on ON_QA state or later to

  reflect this.

  

  Regards

  Fedora Release Engineering

  

- [1] https://fedorapeople.org/groups/schedule/f-N/f-N-key-tasks.html

+ [1] https://fedorapeople.org/groups/schedule/f-fN/f-fN-key-tasks.html

  [2] https://fedoraproject.org/wiki/Updates_Policy#Bodhi_enabling

  [3] https://fedoraproject.org/wiki/Updates_Policy#Branched_release

  [4] https://fedoraproject.org/wiki/Milestone_freezes

@@ -1,22 +1,22 @@ 

- Fedora Linux N Beta Released

+ Fedora Linux fN Beta Released

  ------------------------------------------

  

- The Fedora Project is pleased to announce the immediate availability

- of Fedora N Beta, the next step towards our planned Fedora N release

- at the end of MONTH.

+ The Fedora Project is pleased to announce the immediate availability of

+ Fedora Linux fN Beta, the next step towards our planned Fedora Linux fN

+ release at the end of MONTH.

  

  Download the prerelease from our Get Fedora site:

- * Get Fedora N Beta Workstation: https://getfedora.org/workstation/download/

- * Get Fedora N Beta Server: https://getfedora.org/server/download/

- * Get Fedora N Beta IoT: https://getfedora.org/iot/download/

- * Get Fedora N Beta CoreOS: <LINK NEEDED>

- * Get Fedora N Beta Cloud: <LINK NEEDED>

+ * Get Fedora Linux fN Beta Workstation: https://getfedora.org/workstation/download/

+ * Get Fedora Linux fN Beta Server: https://getfedora.org/server/download/

+ * Get Fedora Linux fN Beta IoT: https://getfedora.org/iot/download/

+ * Get Fedora Linux fN Beta CoreOS: <LINK NEEDED>

+ * Get Fedora Linux fN Beta Cloud: <LINK NEEDED>

  

  Or, check out one of our popular variants, including KDE Plasma, Xfce,

  and other desktop environments:

  

- * Get Fedora N Beta Spins: https://spins.fedoraproject.org/prerelease

- * Get Fedora N Beta Labs: https://labs.fedoraproject.org/prerelease

+ * Get Fedora Linux fN Beta Spins: https://spins.fedoraproject.org/prerelease

+ * Get Fedora Linux fN Beta Labs: https://labs.fedoraproject.org/prerelease

  

  

  ## Beta Release Highlights
@@ -25,7 +25,7 @@ 

  

  For more details about the release, read the full announcement at

  

- * https://fedoramagazine.org/announcing-fedora-N-beta/

+ * https://fedoramagazine.org/announcing-fedora-fN-beta/

  

  or look for the prerelease pages in the download sections at

  

@@ -1,6 +1,6 @@ 

  Hi all,

  

- Today, MMM DD YYYY, is an important day on the Fedora N

+ Today, YYYY-MM-DD, is an important day on the Fedora Linux fN

  schedule [1], with significant cut-offs.

  

  Today we have the Final Freeze [2] which starts at 14:00 UTC. This
@@ -11,8 +11,8 @@ 

  lifted and packages can move to the 'updates' repository, pending

  updates will be pushed before final release as zero day updates.

  

- [1] https://fedorapeople.org/groups/schedule/f-N/f-N-key-tasks.html

+ [1] https://fedorapeople.org/groups/schedule/f-fN/f-fN-key-tasks.html

  [2] https://fedoraproject.org/wiki/Milestone_freezes

  [3] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process

  [4] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process

- [5] https://qa.fedoraproject.org/blockerbugs/milestone/N/final/buglist

+ [5] https://qa.fedoraproject.org/blockerbugs/milestone/fN/final/buglist

@@ -1,19 +1,22 @@ 

  Hello all,

  

- Fedora N will go end of life for updates and support on YYYY-MM-DD

- No further updates, including security updates, will be

- available for Fedora N after the said date. All the updates of Fedora

- N being pushed to stable will be stopped as well.

+ Fedora Linux fN will go end of life for updates and support on

+ YYYY-MM-DD.

+ No more updates of any kind, including security updates or security

+ announcements, will be available for Fedora Linux fN after the said

+ date. All the updates of Fedora Linux fN being pushed to stable will be

+ stopped as well.

  

- Fedora N+1 will continue to receive updates until approximately one

- month after the release of Fedora N+2. The maintenance schedule of

- Fedora releases is documented on the Fedora Project wiki [0]. The

- fedora Project wiki also contains instructions [1] on how to upgrade

- from a previous release of Fedora to a version receiving updates.

+ Fedora Linux fN+1 will continue to receive updates until approximately

+ one month after the release of Fedora Linux fN+2. The maintenance

+ schedule of Fedora Linux releases is documented on the Fedora Project

+ wiki [1]. The Fedora Project wiki also contains instructions[2] on how to

+ upgrade from a previous release of Fedora Linux to a version receiving

+ updates.

  

  Regards,

  Fedora Release Engineering

  

- [0]https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule

- [1]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades

+ [1]https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule

+ [2]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades

  

The current template mentions that no more updates will be provided
for EOL Fedora releases.

This could create the (wrong) impression that the code is still evaluated
for security risks and that just the updates won't happen anymore.

To avoid any misunderstandings:
Add an explicit statement that also no more security announcements will
be made.

Signed-off-by: Manfred Spraul manfred@colorfullife.com

Fair enough. How about "No more updates of any kind, including security... "?

The any kind would then cover anything else people think might still happen?

Hi Kevin,

On 8/9/22 00:47, Kevin Fenzi wrote:

kevin commented on the pull-request: end-of-life template: Explicitly mention no more security announcements that you are following:
``
Fair enough. How about "No more updates of any kind, including security... "?

The any kind would then cover anything else people think might still happen?

The core message should be that all activity will be stopped. No more
package update, but also no more assessments for vulnerabilities, or
anything else.

Thus the fact that e.g. https://www.opencve.io/cve/CVE-2021-44228 lists
only cpe:2.3:o:fedoraproject:fedora:34::::::: and
cpe:2.3:o:fedoraproject:fedora:35:
:::::: must not be interpreted
as "Fedora 33 is not affected".

What would be your wording proposal?

Perhaps, as idea: We could use a positive sentence:

All activities related to Fedora N will be stopped after the said
date. This includes package updates and security assessments.

All the updates of Fedora N being pushed to stable will be stopped as
well.

--

Manfred

Well, the reason I proposed adding "of any kind" is that if we say "no security updates" someone might assume there still were bugfix and enhancement updates.

So, my proposal was your changes with adding "of any kind".

Perhaps @bcotton could have some further ideas?

I think the proposed text with Kevin's addition is good. I was originally going to push back against the "or security updates", but reading Manfred's reasoning in the comments, I think it makes sense. Adding "of any kind" is redundant, but it's a good redundancy in this case. We want to make it very clear that "this is all you get", so a belt-and-suspenders approach makes sense here.

Hi,

On 8/15/22 16:00, Ben Cotton wrote:

bcotton commented on the pull-request: end-of-life template: Explicitly mention no more security announcements that you are following:
I think the proposed text with Kevin's addition is good. I was originally going to push back against the "or security updates", but reading Manfred's reasoning in the comments, I think it makes sense. Adding "of any kind" is redundant, but it's a good redundancy in this case. We want to make it very clear that "this is all you get", so a belt-and-suspenders approach makes sense here.

To reply, visit the link below or just reply to this email
https://pagure.io/releng/pull-request/10951

Updated patch is attached.

--

Manfred

2 new commits added

  • end-of-life template: Explicitly mention no more security announcements
  • Revert "end-of-life template: Explicitly mention no more security announcements"
2 years ago

Attachments didn't work.

Unfortunately I couldn't find how to update a PR, thus here is the
updated patch:

https://pagure.io/fork/manfredcolorfu/releng/c/69ab47f2774a24119ff3c1c4a7d71a3900e63f6b?branch=main

--

Manfred

1 new commit added

  • Revert "end-of-life template: Explicitly mention no more security announcements"
2 years ago

LGTM, although we might want to take this opportunity to say Fedora Linux instead of Fedora:

https://communityblog.fedoraproject.org/fedora-is-a-community-fedora-linux-is-our-os/

Now there's conflicts. ;(

You can update the pr by getting the branch the way you want it locally and then git push --force it. It should update the PR.

3 new commits added

  • end-of-life template: Explicitly mention no more security announcements
  • Revert "end-of-life template: Explicitly mention no more security announcements"
  • end-of-life template: Explicitly mention no more security announcements
2 years ago

rebased onto 6e27edaeb71d7afb3c317c302042b1b33d142375

2 years ago

1 new commit added

  • mail-templates: Update for Fedora Linux instead of Fedora
2 years ago

Hi Kevin,
On 8/29/22 21:59, Kevin Fenzi wrote:

kevin commented on the pull-request: end-of-life template: Explicitly mention no more security announcements that you are following:
``
Now there's conflicts. ;(

Now better?

Open are:

  • sometimes, there is a space before a cross reference, sometimes no space:

"schedule[1]" and "activation point [2]"

  • The date format is mixed: "YYYY-MM-DD", "MMM DD, YYYY" and "MMM DD YYYY"

  • I've replaced the "37" in 01-mass-rebuild-start.txt with N. I do not
    know if this was right.

You can update the pr by getting the branch the way you want it locally and then git push --force it. It should update the PR.

``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/pull-request/10951

I'd say always use a space for references.

date format should be YYYY-MM-DD everywhere.

Replace 37 with 'fN' :)

Can you make those changes and rebase?

rebased onto d9d319a

a year ago

2 new commits added

  • mail-templates: Update for Fedora Linux instead of Fedora, spellings
  • end-of-life template: Explicitly mention no more security announcements
a year ago

Changes and rebase done.
As additional finding: in 07, the references started with [0], in the rest, the references started with [1]. I've changed it to [1] for all files.

Great! Looks ok to me now. Many thanks for the work on it...

Pull-Request has been merged by kevin

a year ago