[interchange-docs] docs - jon modified icdevgroup/release-notes.txt

[docs at icdevgroup.org]

User:      jon
Date:      2008-05-21 23:35:54 GMT
Modified:  icdevgroup release-notes.txt
Log:
Note a few more details about release process.

Revision  Changes    Path
1.8                  docs/icdevgroup/release-notes.txt


rev 1.8, prev_rev 1.7
Index: release-notes.txt
===================================================================
RCS file: /var/cvs/docs/icdevgroup/release-notes.txt,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -u -r1.7 -r1.8
--- release-notes.txt	11 Apr 2008 09:16:53 -0000	1.7
+++ release-notes.txt	21 May 2008 23:35:54 -0000	1.8
@@ -1,5 +1,5 @@
 RELEASING A NEW VERSION OF INTERCHANGE
-$Id: release-notes.txt,v 1.7 2008-04-11 09:16:53 jon Exp $
+$Id: release-notes.txt,v 1.8 2008-05-21 23:35:54 jon Exp $
 
 
 Pre-release:
@@ -41,15 +41,16 @@
 Update interchange-x.y.z.tar.{gz,bz2} and interchange-latest.tar.gz symlinks for stable releases
 Rename README to README.txt so Apache will display it
 Rename README.rpm-dist to README.txt in rpm directory
+Update UPGRADE file to latest
 Update WHATSNEW file to latest (no need to keep old ones in same branch, as their contents are still included in the latest file)
 
 
 Update developer website:
 
 catalog/products/news.txt - announcement
-catalog/products/variable.txt - version variable
-make commit publish
-(or make commit restart if necessary)
+catalog/products/variable.txt - version variable(s)
+make commit publish (or make commit restart if necessary)
+Save ANNOUNCEMENT-x.y.z.txt to icdevgroup.org ftp area, then run user icdevgroup's cron job generate-past-releases-list.pl, which updates the list that the "releases" page uses.
 
 Then verify changes were made:
 
@@ -60,7 +61,7 @@
 
 Make announcements at:
 
-interchange-announce at icdevgroup.org (then upload ANNOUNCEMENT-x.y.z.txt to icdevgroup.org ftp area)
+interchange-announce at icdevgroup.org
 Freshmeat.net
 SourceForge Interchange project: http://sourceforge.net/projects/interchange/