On Sat, Jun 30, 2012 at 3:32 AM, Andrea Aime
<[email protected]>wrote:
> On Sat, Jun 30, 2012 at 10:09 AM, Michael Bedward <
> [email protected]> wrote:
>
>> On 30 June 2012 16:47, Andrea Aime <[email protected]> wrote:
>>
>> > Master wise, if we want to release a milestone, we just tag the master?
>> > However this will require a "out of the pool"
>> > period, even if a small one.
>>
>> My reading of Justin's proposed scheme was that milestones would never
>> be coming from the master branch, and that this would impose a well
>> defined structure on how versions of any kind are issued. But given
>> your question I wonder if I'm missing something ?
>>
>
> What I'm wondering is, how do we change the version numbers to make
> a milestone release without affecting master?
>
>
This is the tricky part. If we didn;t actually have to tag milestones and
betas then we could make this work and just create a short lived release
branch from master, do the changes, release and once published just delete
the release branch when done. Again though there would be no official tag
for the release, or the tag could point to the revision we released from
but would not have the official version numbers set. Not having tags for
milestones and betas might not be a bad thing... as it would prevent the
list of tags in the repo from exploding. Just spitballing here.
>
>> > Assuming we have automation I guess another possible way is to have the
>> > script make the changes
>> > on the stable branch, commit, then commit a revert of those, and then
>> tag
>> > the specific revision number
>> > that had the version number changes as the release... convoluted
>> enough? :-p
>> >
>>
>> Won't the separate release branches be a lot easier than that ? Or is
>> there some cost to maintaining them ?
>>
>
> I don't believe there will be a cost, was more thinking to the plublic
> face of the
> project on github. Look at the branches dropdown here:
> https://github.com/geotools/geotools
>
> I'm wondering if people might get confused by seeing the release branches
> and
> might end up working off those ones instead off the stable or master
> branch.
> Also thinking 2-3 years in the future, having the release branches will
> mean having
> twice as many entries in the dropdown.
> Maybe I'm thinking too much? :-p
>
> Cheers
> Andrea
>
>
> --
> Ing. Andrea Aime
> GeoSolutions S.A.S.
> Tech lead
>
> Via Poggio alle Viti 1187
> 55054 Massarosa (LU)
> Italy
>
> phone: +39 0584 962313
> fax: +39 0584 962313
> mob: +39 339 8844549
>
> http://www.geo-solutions.it
> http://geo-solutions.blogspot.com/
> http://www.youtube.com/user/GeoSolutionsIT
> http://www.linkedin.com/in/andreaaime
> http://twitter.com/geowolf
>
>
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
