Changes between Version 9 and Version 10 of RasdamanReleaseProcess

Timestamp:

Mar 20, 2013, 3:49:59 PM (11 years ago)

Author:

abeccati

Comment:

tag and branch howto

RasdamanReleaseProcess

@@ -55 +55 @@
 Releases can only be made if the [http://rasdaman.eecs.jacobs-university.de/trac/rasdaman/build build status] is successful for the latest (or chosen one for release preparation) commit.
 
- * Create branch and tag according to the aforementioned naming scheme - ''Requires write access to the repo''
- * Create source tarball:
+== 1. Create branch and tag according to the aforementioned naming scheme - ''Requires write access to the repo'' ==
+{{{
+VERSION="v$MAJOR.$MINOR.0"
+RELEASE="release_$MAJOR.$MINOR"
+
+git pull
+git fetch
+
+git tag $VERSION
+git push origin $VERSION
+
+git branch $RELEASE
+git push origin $RELEASE
+}}}
+
+== 2. Create source tarball ==
+
+{{{
    * git archive  --output=rasdaman-community-v8.4.0.tgz v8.4.0   # from local clone
+}}}
+{{{
    * git archive --remote=git://kahlua.eecs.jacobs-university.de/rasdaman.git --output=rasdaman-community-v8.4.0.tgz v8.4.0 # diretly from repo ''currently not working''
- * Build RPM and test it on local system
+}}}
 
-These to be done as close together as possible:
+== 3. Build RPM and test it on local system ==
+
+
+== 4. These to be done as close together as possible ==
  * Update all links to download and RPM repo then
  * Announce release
    * to -dev and -users lists if release candidate / patch
    * also to -announce (to be established) in case of final release
+
 
 = Open issues =
@@ -74 +96 @@
 == Patch manager with branches ==
 Patch manager will be updated to support the branching model.
-