summaryrefslogtreecommitdiff
path: root/DEVELOPMENT
diff options
context:
space:
mode:
authorGunnar Wrobel <wrobel@pardus.de>2007-10-15 15:38:24 (GMT)
committerGunnar Wrobel <wrobel@pardus.de>2007-10-15 15:38:24 (GMT)
commitd0b57dc0b12715a7f9e15ce56d45ae8b3f44536e (patch)
tree9b21886eef8a581bb438cb22339c7b13b4251194 /DEVELOPMENT
parent0e077cd97e7b8b89fb8127cea1870225be84520b (diff)
downloadkolab-server-d0b57dc0b12715a7f9e15ce56d45ae8b3f44536e.tar.gz
Structure.
Diffstat (limited to 'DEVELOPMENT')
-rw-r--r--DEVELOPMENT58
1 files changed, 28 insertions, 30 deletions
diff --git a/DEVELOPMENT b/DEVELOPMENT
index 1ff6953..54df264 100644
--- a/DEVELOPMENT
+++ b/DEVELOPMENT
@@ -1,9 +1,10 @@
Development notes
=================
-The perl-kolab package is a standard perl package meant to be handled
-with the Makefile.PL script. You will receive a standard "Makefile" by
-running "perl Makefile.PL".
+The perl-kolab package is a standard perl package and a Kolab Server
+core component. It is meant to be handled with the Makefile.PL
+script. You will receive a standard "Makefile" by running "perl
+Makefile.PL".
The Kolab Server packages were usually not released as source
packages. This should be changed with this new package layout. The
@@ -15,11 +16,29 @@ OpenPKG system.
Version numbering
=================
-perl-kolab is a Kolab Server core package. 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.
+A NEW VERSION HAS TO BE SET IN
+
+ lib/Kolab.pm
+
+e.g.
+
+our $KOLAB_BASE_VERSION = "2.2.beta1";
+
+Release versions
+----------------
+
+For 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 source packages will look like this:
+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).
+
+Source packages will then look like this:
perl-kolab-2.1.0.tar.gz
@@ -27,9 +46,8 @@ Released source RPMs will look like this:
perl-kolab-2.1.0-20070819.src.rpm
-A NEW VERSION HAS TO BE SET IN
-
- lib/Kolab.pm
+Snapshots
+---------
After tagging and releasing, please set
@@ -48,26 +66,6 @@ Source RPMs will be named similar:
perl-kolab-2.1.0+cvs-20070810.src.rpm
-For 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 reversed:
-
-my $KOLAB_CVS = 0;
-
-Pre-release candidates receive the suffix "betaX" or "rcX" and
-cource packages will then look like this:
-
- perl-kolab-2.2.beta1.tar.gz
-
-Source RPMs will be named accordingly:
-
- perl-kolab-2.2.beta1-20070810.src.rpm
-
-Or, for the cvs versions:
-
- perl-kolab-2.2.beta1+cvs20070810.tar.gz
- perl-kolab-2.2.beta1+cvs-20070810.src.rpm
-
Change log
==========