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

[Paride Legovini]

Add Feature Freeze template

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

[Paride Legovini (paride)]

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

[Brian Murray (brian-murray)]

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

[Paride Legovini (paride)]

MP updated, ready for another review.

[Paride Legovini (paride)]

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:

  VERSION_CODENAME=kinetic

What do you think?

review: Needs Fixing

[Paride Legovini (paride)]

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:).

diff --git a/announcements/feature-freeze b/announcements/feature-freeze
new file mode 100644
index 0000000..d06f8a9
--- /dev/null
+++ b/announcements/feature-freeze
@@ -0,0 +1,23 @@
+To: [e-mail]
+Reply-To: [e-mail]
+Subject: <CODENAME> (to be <VERSION>) now in Feature Freeze
+
+As per the release schedule, <CODENAME> is now in Feature Freeze.
+
+Ideally, you will all now be focusing on bug fixing and not on getting new
+features into the release. However, if necessary, please follow the process
+for freeze exceptions:
+
+  https://wiki.ubuntu.com/FreezeExceptionProcess
+
+As is the custom, packages that have been uploaded to <LOWERCASE CODENAME>-proposed prior
+to the feature freeze deadline, but have gotten stuck there, remain
+candidates for fixing between now and release.
+
+Remember that version strings don't matter for Feature Freeze. If you
+upload a new upstream release and it has no new features then you don't need
+an exception. If you add a debian/patch that adds a new feature, or enable one
+via build flags then you do. We care about the content of the archive, not
+about precisely how things got there.
+
+Happy bug squashing!