[pgrouting-dev] Version numbering suggestion

[Daniel Kastl]

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> 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
> http://lists.osgeo.org/mailman/listinfo/pgrouting-dev
>



-- 
Georepublic UG & Georepublic Japan
eMail: daniel.kastl at georepublic.de
Web: http://georepublic.info
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pgrouting-dev/attachments/20141226/6ef3fbb0/attachment.html>