[Live-demo] 2.0.3 testing

Alex Mandel tech_dev at wildintellect.com
Wed Sep 30 22:53:47 PDT 2009


Hamish wrote:
> Jody wrote:
>> Yep; It is on its way to be printed as we speak.
> 
> In that case I will tag (snapshot) the release it in SVN now.
> Two questions first:
> 
> - what was the final release number used, 2.0.3 or 2.0.4?
> 
> - my plan is in the release branch to search & replace "trunk" with
> "branches/arramagong_2" in the file downloads so scripts find things in 
> their historical places. Thus we can rearrange trunk at will without
> ruining the ability to build 2.0 again. Does that suit everyone? The
> branch is only for important bug fixes for folks rebuilding the image.
> I imaging that after the next development cycle the next branch will be
> called e.g. arramagong_2_1 or so.
> 
> 
> If things change before the VMs come out it doesn't cost much to tag
> a 2.0.5 as well, but if that is to come from trunk we need to be clear
> that the deep-freeze is still in place (that means talk it over with
> Alex before you check anything new in).
> 
> 
> Hamish
> 
> 

2.0.3

Seems to make sense, I think the only place this would apply is the
bootstrap that pulls the svn.

I should probably go through the commit log and give you a list of what
I actually applied, since a lot of changes from 2.0 were done by hand.

Alex



More information about the Osgeolive mailing list