[pgrouting-dev] Version numbering suggestion

[Stephen Woodbridge]

OK, I'm fine with changing the way we do things. I'm not sure what that 
means for changes to the repository without working my way through all 
the changes and testing them. It has been 18+ months since I setup this 
scheme and I don't remember all the details of how things get populated 
and when. I do know that we probably need a script to automate change 
versions when we make a release, because we had a few false starts last 
time making the 2.0 releases.

I'm tied up on some unrelated projects and it will be a while before I 
can get back to doing much on pgrouting.

-Steve

On 12/26/2014 3:53 PM, Paragon Corporation wrote:
>> but it creates the same confusion later because pgrouting-2.0.1 really
> that or some prerelease develop leading up to the the release. This is only
> clear if you look at the full version.
>
>
> That's the reason in PostGIS we don't call it 2.0.1 we call iti 2.0 branch
> but the version number on it is 2.0.1dev so we know it's not a released
> branch.
>
> It's true you can tell by looking at pgr_version() if you look hard enough
> where it came from.
>
> I'm more thinking along the lines of what the extension version says.
>
> It's not an issue for pgRouting at the moment since to upgrade pgrouting you
> just drop the pgrouting extension and then readd it.
>
>
> But -- what happens when people start building functions around the
> pgrouting functions or you have data types used by users, then you have the
> problem that
>
> Your extension is called 2.0.0 in both your release and your minor/micro
> development branch.
>
> So there would be no way for someone to do an extension upgrade, even if you
> supported such a thing.
>
> Thanks,
> Regina
>
>
>
>
> _______________________________________________
> pgrouting-dev mailing list
> pgrouting-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/pgrouting-dev
>