[certi-cvs] certi ReleaseProcess.txt

[certi-cvs]

CVSROOT:        /sources/certi
Module name:    certi
Changes by:     Eric NOULARD <erk>      09/04/30 09:16:47

Modified files:
        .              : ReleaseProcess.txt 

Log message:
        Update release process

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/certi/ReleaseProcess.txt?cvsroot=certi&r1=1.4&r2=1.5

Patches:
Index: ReleaseProcess.txt
===================================================================
RCS file: /sources/certi/certi/ReleaseProcess.txt,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- ReleaseProcess.txt  25 Jun 2008 09:00:06 -0000      1.4
+++ ReleaseProcess.txt  30 Apr 2009 09:16:46 -0000      1.5
@@ -38,7 +38,9 @@
 
      Better is at least 2 built:
          Linux ix86 wth gcc  (32bits)
-         Windows win32 with Visual Studio or Wascana
+         Windows win32 with Visual Studio 
+                     and/or Code::Blocks (http://www.codeblocks.org/)
+                     and/or Wascana (http://wascana.sourceforge.net/)          
           
 
 6) Run autotests :))
    Which means for today run as many tests as you can do
@@ -75,7 +77,7 @@
    Fix packaging trouble if any and move the previous tag 
    if any commit occured.
 
-10) digitally sign the packages you made and put them
+10) Digitally sign the packages you made and put them
    in the download area:
    https://savannah.gnu.org/maintenance/DownloadArea
 
@@ -84,7 +86,7 @@
 11) Check is the download area has been properly updated
      http://download.savannah.nongnu.org/releases/certi/
 
-12) post the appropriate news on Savannah CERTI pages
+12) Post the appropriate news on Savannah CERTI pages
    https://savannah.nongnu.org/news/submit.php?group=certi
 
    DON'T MAIL to certi-devel since news are 
@@ -93,5 +95,8 @@
    Remember that once you have posted the news you should
    approve it before it appears on first page.
 
+13) OPTIONNALLY update online CERTI documentation at 
+        http://www.nongnu.org/certi
+
 You are right this process IS painful and should be automated (a lot...)
 be sure we are working on it :))