[postgis-devel] 1, dot, 3 dot 4!

[Kevin Neufeld]

Ok, so after thinking about this some more, to avoid naming collisions 
with autobuilds and tagging, I propose that instead of:

1. update devel branch/trunk "Version.config" to tagged version.
2. create a tag release
3. revert "Version.config" in devel branch/trunk back to SVN version

we follow this procedure:

1. create a tag release
2. svn switch to tag release and update "Version.config" in the new 
tagged release.

I know it's not normal to commit to a tagged release, but updating the 
version would be the *only* commit to the newly created tag.

Doing things this way would simplify things in the autobuilding 
department since nothing is changing in the devel branch - folks can 
continue to happily commit without worries.

Eventually, when 1.3.4 is tagged, branch would get updated to 1.3.5SVN 
at the same time - naming collisions are still avoided.

Thoughts?
-- Kevin

Obe, Regina wrote:
> Paul,
> 
> Hmm - I just downloaded the
> http://postgis.refractions.net/download/postgis-1.3.4rc1.tar.gz
> 
> and it has an inner folder 
> 
> postgis-1.3.4svn
> 
> I suspect this may cause some people some confusion?
> 
>  Why is the date listed as Oct 12th? I thought you released that just
> recently in the past day or so? 
> 
> Thanks,
> Regina
> -----------------------------------------
> The substance of this message, including any attachments, may be
> confidential, legally privileged and/or exempt from disclosure
> pursuant to Massachusetts law. It is intended
> solely for the addressee. If you received this in error, please
> contact the sender and delete the material from any computer.
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel