summaryrefslogtreecommitdiff
path: root/DEVELOPMENT
diff options
context:
space:
mode:
authorThomas Arendsen Hein <thomas@intevation.de>2007-10-15 16:21:07 (GMT)
committerThomas Arendsen Hein <thomas@intevation.de>2007-10-15 16:21:07 (GMT)
commitbf7c6c7ad53aab7204bb85970f7e214d8210a189 (patch)
treee900df26274b01d9ffe9f8bd62c741307163a1e2 /DEVELOPMENT
parentd0b57dc0b12715a7f9e15ce56d45ae8b3f44536e (diff)
downloadkolab-server-bf7c6c7ad53aab7204bb85970f7e214d8210a189.tar.gz
Improved paragraph about version numbering
Diffstat (limited to 'DEVELOPMENT')
-rw-r--r--DEVELOPMENT49
1 files changed, 26 insertions, 23 deletions
diff --git a/DEVELOPMENT b/DEVELOPMENT
index 54df264..012c3af 100644
--- a/DEVELOPMENT
+++ b/DEVELOPMENT
@@ -13,58 +13,60 @@ distributed as source package. The same run will produce a
perl-kolab-*.src.rpm package that is suited for installation on an
OpenPKG system.
+
Version numbering
=================
-A NEW VERSION HAS TO BE SET IN
+The package version will be set in
lib/Kolab.pm
e.g.
-our $KOLAB_BASE_VERSION = "2.2.beta1";
+ our $KOLAB_BASE_VERSION = "2.2.beta1";
+ my $KOLAB_CVS = 1;
Release versions
----------------
-For tagging the next release the version number needs to be increased
+Released packages should have the same core version as the server
+release. As a part of Kolab Server 2.2.0 the version number should be
+2.2.0. Pre-release candidates receive the suffix "betaX" or "rcX"
+(e.g. 2.2.beta1).
+
+Before tagging the next release the version number needs to be increased
to the new Kolab Server version (e.g. 2.2.0) and the CVS switch needs to
be set to 0:
-my $KOLAB_CVS = 0;
-
-Released packages should have the same core version as the Server
-release. As a part of Kolab Server 2.1.0 the version number should be
-2.1.0. Pre-release candidates receive the suffix "betaX" or "rcX"
-(e.g. 2.2.beta1).
+ our $KOLAB_BASE_VERSION = "2.2.0";
+ my $KOLAB_CVS = 0;
-Source packages will then look like this:
+After updating $KOLAB_BASE_VERSION and $KOLAB_CVS you can commit these
+changes and tag the release.
- perl-kolab-2.1.0.tar.gz
+Now you can create source tarballs and RPMs which will look like:
-Released source RPMs will look like this:
+ perl-kolab-2.2.0.tar.gz
+ perl-kolab-2.2.0-20070819.src.rpm
- perl-kolab-2.1.0-20070819.src.rpm
+Don't forget to change $KOLAB_CVS back to 1 again and commit, so later
+CVS snapshots will be named correctly.
Snapshots
---------
-After tagging and releasing, please set
-
-my $KOLAB_CVS = 1;
+Make sure lib/Kolab.pm contains the following line:
-in lib/Kolab.pm.
+ my $KOLAB_CVS = 1;
The release number will then receive the suffix "+cvs" and the current
-date will be appended.
+date will be appended.
-Source packages will then look like this:
+Source tarballs and RPMs will then look like this:
- perl-kolab-2.1.0+cvs20070810.tar.gz
+ perl-kolab-2.2.0+cvs20070810.tar.gz
+ perl-kolab-2.2.0+cvs-20070810.src.rpm
-Source RPMs will be named similar:
-
- perl-kolab-2.1.0+cvs-20070810.src.rpm
Change log
==========
@@ -72,6 +74,7 @@ Change log
The change log for the package is provided in "Changes". Please keep
this file up-to-date if you change the source code of this package.
+
Contributors
============