Changes between Version 8 and Version 9 of RasdamanReleaseProcess

Timestamp:

Mar 19, 2013, 12:37:43 PM (13 years ago)

Author:

abeccati

Comment:

release process (steps)

RasdamanReleaseProcess

@@ -10 +10 @@
 Versions are numbered according to [http://semver.org semantic versioning] (we may reference the fields X.Y.Z as M.m.p to better indicate Major, minor and patch numbering), starting with 8.4.0. Tentative interface definition is defined by the standards supported in the [wiki:Features features matrix] and the command line tools parameters.
 
-= Initial process =
+= Branching model =
 
 A single main repository is maintained (as we already have).
@@ -51 +51 @@
 
 
-Releases can only be made if the [http://rasdaman.eecs.jacobs-university.de/trac/rasdaman/build build status] is successful for the latest commit.
+= Initial process =
+
+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:
+   * 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:
+ * 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 =
@@ -61 +75 @@
 Patch manager will be updated to support the branching model.
 
-== Tags ==
-Do tags belong to a branch or are they still visible repository wide on git?
- * Looks like tags are still repository wide, need to be tested with tags on remote branches.