Changes between Version 143 and Version 144 of TracDev/ReleaseChecklist

Timestamp:

Aug 22, 2019, 11:53:52 PM (5 years ago)

Author:

Ryan J Ollos

Comment:

Some steps for a major release moved to internal (private) "how to release" page.

TracDev/ReleaseChecklist

@@ -53 +53 @@
 
  * Update the TracChangeLog page.
+ * Check TracDev/ReleaseNotes, go through the tickets which have an empty //Release Notes// field and say a word there.
  * For major releases:
   * Verify TracInstall and TracUpgrade.
-  * Check TracDev/ReleaseNotes, go through the tickets which have an empty //Release Notes// field and say a word there.
   * Check TracDev/ApiChanges.
 
@@ -63 +63 @@
 
  * Verify that TracStandalone#Reference matches current `tracd --help`.
- * Update browser source TracLinks that point to t.e.o (e.g. `trac:browser:branches/1.2-stable`) to the latest stable release //(*)//.
+ * Update browser source TracLinks that point to t.e.o (e.g. `trac:browser:branches/1.2-stable`) to the latest stable release.
  {{{#!sh
 $ grep --color -R -E "trac:(source|browser|repos):" trac/wiki/default-pages/ --exclude=TracChangeLog --exclude=TracLinks
 }}}
- * Update [source:trunk/RELEASE.rst RELEASE.rst] from wiki TracChangeLog (File is named `RELEASE` for Trac < 1.2) //(*)//.
+ * Update [source:trunk/RELEASE.rst RELEASE.rst] from wiki TracChangeLog (File is named `RELEASE` for Trac < 1.2).
  * [TracProject/DefaultWikiPages#sync Sync] the wiki.
  {{{#!sh
@@ -197 +197 @@
  * Update version number in [source:trunk/setup.py setup.py] and [source:trunk/trac/__init__.py trac/__init__.py].
  * Create a release coordination ticket with keyword [kwquery:release]. The //Clone// button can be used on the previous release coordination ticket to pre-populate the fields.
- * For major releases, update the RoadMap and add a report //Active Tickets for 1.x// (e.g. {42}).
 
 //(*) not for beta or rc releases//