rc-release-ann.ezt

Checkout Tools
  • last updated 1 hour ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Add 'Reply-To: users@' in the 'release.py write-announcement' templates.
  1. … 1 more file in changeset.
No longer produce SHA1 checksums for release tarballs.

Per ASF policy: https://www.apache.org/dev/release-distribution#sigs-and-sums

* tools/dist/release.py

(roll_tarballs): Don't create .sha1 files.

(get_sha1info): Rename to 'get_fileinfo'. Only return filenames.

(write_announcement): Don't fetch SHA1 info.

(write_downloads): Track the rename.

* tools/dist/templates/download.ezt,

tools/dist/templates/rc-release-ann.ezt,

tools/dist/templates/stable-release-ann.ezt

Remove SHA1 listings.

  1. … 3 more files in changeset.
* tools/dist/templates/rc-release-ann.ezt: use https-links only

* tools/dist/templates/stable-release-ann.ezt: the same

  1. … 1 more file in changeset.
Add unsubscribe info to the release announcement email templates.
  1. … 1 more file in changeset.
* tools/dist/templates/rc-release-ann.ezt: Typo fix.

Patch by: Pavel Lyalyakin <pavel.lyalyakin{_AT_}visualsvn.com>

* tools/dist/templates/rc-release-ann.ezt: Change the "known issues" link

to something that is more likely to work for 1.11 prereleases too.

* tools/dist/templates/rc-release-ann.ezt: Update for issue tracker migration

from tigris to jira.

release.py: Add details to email announcements.

* tools/dist/templates/rc-announce-ann.ezt,

* tools/dist/templates/stable-announce-ann.ezt:

Say "This is a feature/security/bugfix release"

and "Subversion is an open-source version control system" [quoted

from our homepage] to make the announcements self-contained for

readers of announce_at_apache.org and other aggregators.

* tools/dist/release.py

(): Tell Python this file is UTF-8 encoded, because there is a UTF-8 comment.

(ezt_False, ezt_True, ezt_bool): New.

(write_announcement): Pass two new parameters, 'security' and 'dot-zero',

to the ezt templates.

(main): New --security option to write-announcement.

Suggested by: sebb

Apologies to: gstein

(for that ezt API workaround)

  1. … 2 more files in changeset.
* tools/dist/templates/rc-release-ann.ezt,

* tools/dist/templates/stable-release-ann.ezt:

Fix a copy-pasto in these templates.

  1. … 1 more file in changeset.
release.py: Link to SHA-512 checksums from email release announcements.

* tools/dist/templates/rc-release-ann.ezt,

* tools/dist/templates/stable-release-ann.ezt:

As above. Use an https://www.apache.org/dist/ link as on download pages.

  1. … 1 more file in changeset.
* tools/dist/templates/rc-release-ann.ezt: Unbreak, after r1800799.
release.py: Save the RM a bit more typing.

* tools/dist/templates/rc-release-ann.ezt,

* tools/dist/templates/stable-release-ann.ezt:

Generate the Subject/To/CC (as per HACKING) and a From reminder.

  1. … 1 more file in changeset.
Update download links in the news and release notice templates.

* tools/dist/templates/rc-news.ezt,

tools/dist/templates/rc-release-ann.ezt,

tools/dist/templates/stable-news.ezt,

tools/dist/templates/stable-release-ann.ezt:

Point to /download.cgi instead of the obsolete and nonexistent /download/.

  1. … 3 more files in changeset.
Fix release.py write-announcement to be aware of the anchor.

I've made a long string of releases with the wrong anchor for 1.7.x.

This isn't perfect since we have to remember to bump the version before

using the tool when making a new minor, but it help reduce the problem.

* tools/dist/release.py

(recommended_release): New variable to keep track of our recommended line.

(write_announcement): Set the tags based on the version number and avoid

calculating the major/minor string twice.

* tools/dist/templates/rc-release-ann.ezt

tools/dist/templates/stable-release-ann.ezt: Use anchor data instead of hard

coded anchor values.

  1. … 2 more files in changeset.
* tools/dist/templates/rc-release-ann.ezt:

Direct people to the pre-releases section of the download page.

release.py: For the signature info in the release announcement, just read

a pre-existing file. Definitely a hack.

* tools/dist/templates/stable-release-ann.ezt,

tools/dist/templates/rc-release-ann.ezt:

Fixup whitespace.

* tools/dist/release.py

(write_announcement):

Read the existing 'getsigs-output' file for the signature info.

  1. … 2 more files in changeset.
release.py: Provide sha1 and release information when writing announcements.

This is still a bit hacked, but works.

* tools/dist/templates/stable-release-ann.ezt,

tools/dist/templates/rc-release-ann.ezt:

Iterate over the provided sha1 info.

* tools/dist/release.py

(get_sha1info): New.

(write_announcement): Use actual values for the sha1 info and version numbers.

  1. … 2 more files in changeset.
Add a template for the pre-release announcement mails.

* tools/dist/templates/rc-release-ann.ezt:

New.

* tools/dist/release.py

(write_announcement): Add an extra (still bogus) value to the data dict.

  1. … 1 more file in changeset.