You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spamassassin.apache.org by si...@apache.org on 2022/12/14 05:41:43 UTC

svn commit: r1905977 - /spamassassin/trunk/build/README

Author: sidney
Date: Wed Dec 14 05:41:43 2022
New Revision: 1905977

URL: http://svn.apache.org/viewvc?rev=1905977&view=rev
Log:
Clarify some instructions in build README. Move reminder to check some doc files to before it is too late to include the changes in the release build

Modified:
    spamassassin/trunk/build/README

Modified: spamassassin/trunk/build/README
URL: http://svn.apache.org/viewvc/spamassassin/trunk/build/README?rev=1905977&r1=1905976&r2=1905977&view=diff
==============================================================================
--- spamassassin/trunk/build/README (original)
+++ spamassassin/trunk/build/README Wed Dec 14 05:41:43 2022
@@ -229,6 +229,19 @@ Run "svn status" to ensure you're buildi
   perform commits to public SVN repos, you can defer this step until
   later.)
 
+- If there are any issues to note, make sure to edit the UPGRADE file.
+  Every x.x.0 release at a minimum should include a section.
+
+- Check the README file for any items to change.
+
+- Review the CREDITS to update Committers - https://whimsy.apache.org/
+  can help with this.
+
+- Review the CREDITS to update Copyright
+
+- Review the Project Branding Report Checklist at
+  https://www.apache.org/foundation/marks/pmcs
+
 - SVN tag the release files.  This is done using "svn copy".
 
   - For a maintenance release (x.y.1, x.y.2):
@@ -295,7 +308,8 @@ Run "svn status" to ensure you're buildi
   to ensure that the code in this build directory matches up using
   some other mechanism, since SVN is public.)
 
-- run "./build/update_stable" to build the tar.gz, tar.bz2 and zip files.
+- use the following commands to run build/update_stable to build
+  the tar.gz, tar.bz2 and zip files into ~/public_html/devel/
 
     NOTE: link rules, t.rules and rulesrc to a trunk checkout if needed!
 
@@ -306,9 +320,6 @@ Run "svn status" to ensure you're buildi
     ln -s ~/usr/src/Mail-SpamAssassin/trunk/t.rules
     ./build/update_stable
 
-  NOTE: running gpg-agent with the proper homedir is needed for
-  non-privileged users.
-
   The above places files in ~/public_html/devel/
 
 - test the files!  redo until they work!! ;)
@@ -325,19 +336,6 @@ Run "svn status" to ensure you're buildi
   NOTE: Here's a quick example to concat the checksums:
         ls *3.4.2* | grep sha | xargs cat --
 
-- If there are any issues to note, make sure to edit the UPGRADE file.
-  Every x.x.0 release at a minimum should include a section.
-
-- Check the README file for any items to change.
-
-- Review the CREDITS to update Committers - https://whimsy.apache.org/
-  can help with this.
-
-- Review the CREDITS to update Copyright
-
-- Review the Project Branding Report Checklist at
-  https://www.apache.org/foundation/marks/pmcs
-
 - (for any rc, prerelease, or full release) Place the tarballs in a
   discreet location (discreet means not linked from the "downloads" page
   of the website, but included in the vote mail) and request a vote on the