[openorb-commits] CVS: admin/release HOWTO,1.6,1.7

[<lk...@us...>]

Update of /cvsroot/openorb/admin/release
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv32212/release

Modified Files:
	HOWTO 
Log Message:
added release instructions posted by Michael some time ago

Index: HOWTO
===================================================================
RCS file: /cvsroot/openorb/admin/release/HOWTO,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -d -r1.6 -r1.7
--- HOWTO	29 Jul 2004 09:36:26 -0000	1.6
+++ HOWTO	20 Mar 2005 12:46:04 -0000	1.7
@@ -52,6 +52,57 @@
   o website (no release)
 
 
+Release Process
+===============
+
+All the docs or scripts are in the admin module.
+
+Quick HOWTO, using release 1.4.0 as an example:
+0. Get a fresh HEAD revision of all modules:
+    cvs co OpenORBAll
+    cvs co admin
+    cvs co native
+1. Perform a release build: ./admin/bin/build.sh release
+2. Add a release line with the tag name into the WHATSNEW file:
+    Version 1.4.0 - November, 12 2004 - OpenORB_1_4_0_FINAL
+3. When everything is ok (tests are working), create the tag
+   (see admin/release/HOWTO) for the tag and branch names).
+4. Then do a fresh checkout from the tag and rerun the build
+    by using the buildtagged.sh script.
+5. Afterwards you will have a SFUP (SourceForge UPload)
+    folder in TCOO_HOME.
+6. Using the upload.sh script allows you to upload all
+    files into the SF upload area.
+7. The next step is to go to the SF File Release System
+    and follow the steps:
+    Step1:
+    - For each module "Add Release": 1.4.0
+    - Use the same "Release Date" for all modules.
+    - Paste the Changelog from 1.3.0 to 1.4.0
+       into the "Paste The Change Log In:" box
+      (preserve my preformatted text).
+    Step2:
+    - Select the files for this module.
+       ATTENTION: The files must be fully uploaded!
+       If you select the files whilke they are being uploaded
+       you will end up with broken archives!
+    Step 3:
+    - Select "Processor: Platform Independent",
+             "Release Date: 2004-11-12" (example)
+             "File Type: Source .gz, Source .zip, .gz, .zip"
+    Step 4:
+    - Send all users monitoring the release a notification.
+8. Finally you can declare former BETAx releases as "hidden".
+9. Write the release notes with the major
+10. The OpenORB homepage will get updated automatically when
+    you post the release notes as project news.
+11. Announce the release by posting the release notes.
+    (The release notes should finally be added to
+     admin/release/RELEASE_NOTES_1_4_0.txt)
+
+I guess the native module will not be included in the automatic build 
+scripts and should either be added or built manually.
+
 
 Announments:
 ============