[pgrouting-dev] Version numbering suggestion

[Stephen Woodbridge]

Hi Regina,

Rightly or wrongly the versioning that I was trying to impose (assuming 
I remember this correctly) was something along the line of:

Master should represent the current stable tagged released version. 
(currently 2.0.0)

We created branches:

  develop-2_0_1 from the 2.0.0 released master for bug fixes, probably 
have not toggled the version number yet because it is a "develop" branch

  develop from the 2.0.0 released master for the next release aka: 2.1.0 
but probably have not toggled the version number as it is a "develop" 
branch and we had no plan for the next release.

There are a lot of other branches that can be ignored and will get 
cleaned up when we tackle the next release.

Maybe you can explain the versioning that postgis uses and what events 
you use to change version numbers.

For us, develop is always the NEXT major in development release branch
and develop_X_X_X is a minor development bugfix release branch. And 
master is the current stable tagged release.

I'm not opposed to changing this to make it easier for others to work 
with us. This is just what I thought other projects were doing and 
seemed to be a logical and simple to follow process.

Input is always welcome.

Thanks,
   -Steve


On 12/25/2014 8:00 PM, Daniel Kastl wrote:
> Hi Regina,
>
> What you propose is probably what we want(ed) to do.
> Eventually there is a problem with our pre-commit hook:
> https://github.com/pgRouting/pgrouting/blob/master/tools/pre-commit
>
> Probably the failure is, that this hook needs to be copied manually into
> the .git/hooks directory after a new clone, and it's too easy to forget
> this. It actually happened to me ;-)
>
> Thanks for the notice!
> Daniel
>
>
>
>
> On Fri, Dec 26, 2014 at 8:18 AM, Paragon Corporation <lr at pcorp.us
> <mailto:lr at pcorp.us>> wrote:
>
>     I'm not sure if there is a reason for this, so take this as a
>     suggestion and
>     shoot me down if I am out of place suggesting this.
>
>     I think the version number for new branches should be bumped to minimize
>     confusion with the stable branch.
>
>     As I noted before the develop branch still has version number 2.0.0
>     which is
>     really confusing since technically it should be 2.1.0 or better
>     2.1.0dev to
>     reflect it hasn't been released yet and has more or less functions
>     than the
>     previous.
>
>     To a less important extent, the master branch should be bumped to
>     2.0.1 or
>     2.0.1dev.
>
>
>     I must add that PostgreSQL, PostGIS, and GEOS all follow the pattern of
>     bumping up their versions when they start a new development branch
>     or after
>     they tag a stable branch.
>
>
>     Thanks,
>     Regina
>
>
>     _______________________________________________
>     pgrouting-dev mailing list
>     pgrouting-dev at lists.osgeo.org <mailto:pgrouting-dev at lists.osgeo.org>
>     http://lists.osgeo.org/mailman/listinfo/pgrouting-dev
>
>
>
>
> --
> Georepublic UG & Georepublic Japan
> eMail: daniel.kastl at georepublic.de <mailto:daniel.kastl at georepublic.de>
> Web: http://georepublic.info
>
>
>
>
>
> _______________________________________________
> pgrouting-dev mailing list
> pgrouting-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/pgrouting-dev
>