Merge ~paride/ubuntu-release-tools/+git/templates:add-featurefreeze-template into ~ubuntu-release/ubuntu-release-tools/+git/templates:main

Proposed by Paride Legovini
Status: Merged
Merged at revision: bec2405e3a3f4de9badb071aa80d7eadd3f4f035
Proposed branch: ~paride/ubuntu-release-tools/+git/templates:add-featurefreeze-template
Merge into: ~ubuntu-release/ubuntu-release-tools/+git/templates:main
Diff against target: 29 lines (+23/-0)
1 file modified
announcements/feature-freeze (+23/-0)
Reviewer Review Type Date Requested Status
Paride Legovini (community) Needs Fixing
Brian Murray Needs Fixing
Ubuntu Release Team Pending
Review via email:

Commit message

Add Feature Freeze template

To be used for both LTS and non-LTS releases.

To post a comment you must log in.
Revision history for this message
Paride Legovini (paride) wrote :

There's a little different with respect to the other templates: a "Subject" header line, to be used in emails and possibly discourse posts.

Revision history for this message
Brian Murray (brian-murray) wrote :

I think having the Subject is a nice addition and also think adding the destinations might be helpful too. Just a couple of nits to address.

review: Needs Fixing
Revision history for this message
Paride Legovini (paride) :
Revision history for this message
Paride Legovini (paride) wrote :

MP updated, ready for another review.

Revision history for this message
Paride Legovini (paride) wrote :

That's still not consistent, as the discourse links want

  <LOWERCASE NAME> -> adjective-animal

while we want only the adjective here. I could use <VERSION CODENAME> in the feature-freeze template, which matches this entry in /etc/os-release:


What do you think?

review: Needs Fixing
Revision history for this message
Paride Legovini (paride) wrote :

Looks like we're not very consistent in how we call those names, and I don't want to bikeshed too much. The one you suggested (<LOWERCASE CODENAME>) is clear enough.

I added some more headers to the template (To: and Reply-To:).

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
diff --git a/announcements/feature-freeze b/announcements/feature-freeze
0new file mode 1006440new file mode 100644
index 0000000..d06f8a9
--- /dev/null
+++ b/announcements/feature-freeze
@@ -0,0 +1,23 @@
3Subject: <CODENAME> (to be <VERSION>) now in Feature Freeze
5As per the release schedule, <CODENAME> is now in Feature Freeze.
7Ideally, you will all now be focusing on bug fixing and not on getting new
8features into the release. However, if necessary, please follow the process
9for freeze exceptions:
13As is the custom, packages that have been uploaded to <LOWERCASE CODENAME>-proposed prior
14to the feature freeze deadline, but have gotten stuck there, remain
15candidates for fixing between now and release.
17Remember that version strings don't matter for Feature Freeze. If you
18upload a new upstream release and it has no new features then you don't need
19an exception. If you add a debian/patch that adds a new feature, or enable one
20via build flags then you do. We care about the content of the archive, not
21about precisely how things got there.
23Happy bug squashing!


People subscribed via source and target branches