ubuntu-release-tools

Merge ~paelzer/ubuntu-release-tools/+git/templates:notify-about-post-freeze-changes into ~ubuntu-release/ubuntu-release-tools/+git/templates:main

  1. Git
  2. lp:~paelzer/ubuntu-release-tools/+git/templates
  3. notify-about-post-freeze-changes
  4. Merge into main
Proposed by Christian Ehrhardt 
Status: Needs review
Proposed branch: ~paelzer/ubuntu-release-tools/+git/templates:notify-about-post-freeze-changes
Merge into: ~ubuntu-release/ubuntu-release-tools/+git/templates:main
Diff against target: 30 lines (+15/-0)
1 file modified
announcements/final-freeze (+15/-0)
Reviewer Review Type Date Requested Status
Steve Langasek Needs Fixing
Łukasz Zemczak conceptual Approve
Review via email: mp+433265@code.launchpad.net
To post a comment you must log in.
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

I don't mind including this information in the e-mail. The format you proposed also seems sane, but I'd like someone with better 'language-foo' than me commenting if this 'feels' correctly phrased.

review: Approve (conceptual)
Reply
Revision history for this message
Steve Langasek (vorlon) :
review: Needs Fixing
Reply

Unmerged commits

86e7694... by Christian Ehrhardt 

Notify about coming changes as part of the FF mail

Signed-off-by: Christian Ehrhardt <email address hidden>

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
diff --git a/announcements/final-freeze b/announcements/final-freeze
index 1fc6e71..9353aee 100644
--- a/announcements/final-freeze
+++ b/announcements/final-freeze
@@ -24,6 +24,19 @@ yourself if the current state is "good enough", compared to the burden of
24trying to fix all the bugs you might accidentally be introducing with your24trying to fix all the bugs you might accidentally be introducing with your
25shiny new upload.25shiny new upload.
2626
27Speaking of burden, due to the way upstream releases align there are a few
28known "Planned and potentially disruptive archive-wide activities" still
29ahead of us that you should be aware of, despite entering feature freeze.
30Those are:
31 - TODO fetch known entries from [1]
32 - TODO examples of Lunar
33 - TODO March 16th - LLVM 16
34 - TODO March 23 - Gnome 44.0
35 - TODO and list them here so people can see them
36 - TODO without having to click on a link
37 - TODO and update the [1] link below to match the current release
38See [1] for an updated list of such changes.
39
27We will shut down cronjobs and spin some RC images over the next couple of40We will shut down cronjobs and spin some RC images over the next couple of
28days (maybe even on Friday) once the archive and proposed-migration have41days (maybe even on Friday) once the archive and proposed-migration have
29settled a bit, and we expect everyone with a vested interest in a flavour (or42settled a bit, and we expect everyone with a vested interest in a flavour (or
@@ -31,3 +44,5 @@ two) and a few spare hours here and there to get to testing to make sure we
31have another uneventful release next week. Last minute panic is never fun.44have another uneventful release next week. Last minute panic is never fun.
3245
33On behalf of the Ubuntu Release Team,46On behalf of the Ubuntu Release Team,
47
48[1]: https://discourse.ubuntu.com/t/lunar-lobster-release-schedule/27284

Subscribers

People subscribed via source and target branches