Author: turnstep
Date: Sun Aug  5 18:25:36 2007
New Revision: 9822

Modified:
   DBD-Pg/trunk/Changes
   DBD-Pg/trunk/META.yml
   DBD-Pg/trunk/Makefile.PL
   DBD-Pg/trunk/Pg.pm
   DBD-Pg/trunk/README
   DBD-Pg/trunk/README.dev

Log:
Bump the major version number, and switch to three-numbered system.


Modified: DBD-Pg/trunk/Changes
==============================================================================
--- DBD-Pg/trunk/Changes        (original)
+++ DBD-Pg/trunk/Changes        Sun Aug  5 18:25:36 2007
@@ -1,6 +1,7 @@
 ('GSM' is Greg Sabino Mullane, [EMAIL PROTECTED])
 
-1.50
+2.0.0
+       - Change versioning system to three numbered system.
        - Add support for arrays: can pass in arrayrefs to execute, and 
                they are automatically returned as arrays when fetching. [GSM]
        - Overhauled the data type system. [GSM]

Modified: DBD-Pg/trunk/META.yml
==============================================================================
--- DBD-Pg/trunk/META.yml       (original)
+++ DBD-Pg/trunk/META.yml       Sun Aug  5 18:25:36 2007
@@ -1,6 +1,6 @@
 --- #YAML:1.0
 name                : DBD-Pg
-version             : 1.50
+version             : 2.0.0
 abstract            : DBI PostgreSQL interface
 author:              
   - Greg Sabino Mullane <[EMAIL PROTECTED]>

Modified: DBD-Pg/trunk/Makefile.PL
==============================================================================
--- DBD-Pg/trunk/Makefile.PL    (original)
+++ DBD-Pg/trunk/Makefile.PL    Sun Aug  5 18:25:36 2007
@@ -8,7 +8,7 @@
 use DBI 1.45;
 use DBI::DBD;
 
-my $VERSION = '1.50';
+my $VERSION = '2.0.0';
 
 my $lib;
 BEGIN {

Modified: DBD-Pg/trunk/Pg.pm
==============================================================================
--- DBD-Pg/trunk/Pg.pm  (original)
+++ DBD-Pg/trunk/Pg.pm  Sun Aug  5 18:25:36 2007
@@ -16,7 +16,7 @@
 {
        package DBD::Pg;
 
-       our $VERSION = '1.50';
+       our $VERSION = '2.0.0';
 
        use DBI ();
        use DynaLoader ();
@@ -1582,7 +1582,7 @@
 
 =head1 VERSION
 
-This documents version 1.50 of the DBD::Pg module
+This documents version 2.0.0 of the DBD::Pg module
 
 =head1 SYNOPSIS
 

Modified: DBD-Pg/trunk/README
==============================================================================
--- DBD-Pg/trunk/README (original)
+++ DBD-Pg/trunk/README Sun Aug  5 18:25:36 2007
@@ -6,7 +6,7 @@
 DESCRIPTION:
 ------------
 
-This is version 1.50 of DBD-Pg.  The web site for this interface is at:
+This is version 2.0.0 of DBD-Pg.  The web site for this interface is at:
 
        http://search.cpan.org/~dbdpg/
 

Modified: DBD-Pg/trunk/README.dev
==============================================================================
--- DBD-Pg/trunk/README.dev     (original)
+++ DBD-Pg/trunk/README.dev     Sun Aug  5 18:25:36 2007
@@ -478,17 +478,17 @@
 == Version Numbers ==
 =====================
 
-Version numbers are constrained by the Perl CPAN system, in which there is a 
major 
-and a minor number. Generally, we increment the minor version by one for each 
new 
-release. More major releases can bump up to the next "tens" place, e.g. from 
1.33 
-to 1.40. Very major releases can bump the major number, but this should be an 
-extremely rare event. When in doubt, ask on the list. Any bump other than a 
single 
-increment should always be discussed there first anyways.
+Version numbers follow the Postgres convention: major, minor, and revision. 
(Note: older versions 
+of DBD::Pg used a two-number system up until version 1.49, after which it 
switched to 2.0.0).
+The major number should very, very rarely change, and is saved for the truly 
major changes 
+(e.g. those that may cause backwards compatibility problems). The minor 
revision is used to 
+indicate a change in functionality, new features, etc. The revision number is 
used for small 
+tweaks and bug fixes, and must be completely compatible with the version 
before it.
 
 Beta versions are simply the number *before* the new anticipated number, plus 
an 
 underscore to indicate the beta version. For example, if the current version 
is 
-1.41 and you are making betas for an upcoming 1.42 version, you should name 
the 
-beta version as 1.41_1. A second beta would be 1.41_2, etc.
+2.1.4 and you are making betas for an upcoming 2.2.4 version, you should name 
the 
+beta version as 2.2.4_1. A second beta would be 2.2.4_2, etc.
 
 Version numbers are currently set in five files:
 

Reply via email to