Howdy.  Sounds good.  So I have pull a dev branch and made STv4 code gen 
changes (parrt.dev).  We can now pull main to a v3 branch (from which we get 
3.4 release when ready).  I can then push my STv4 stuff back to mainline which 
will now become v4 main.  Is this the picture:

<<inline: branching.gif>>


Ter

On Mar 8, 2011, at 7:29 AM, Jim Idle wrote:

> Sounds reasonable, but it Is trivial to rebranch back in to the regular
> structure with a  more appropriate name. we would send the current main to
> be 3.3.2 (or perhaps 3.4) then whan that is done, take the changes over to
> your branch, then bring your branch back as the main branch, which will
> become v4 in good time. Need a 3.4.1? Just a branch from 3.4 instead of
> main. This is also a lot easier than me rewriting all the build notes ;-)
> 
> I will handle all the integrations when we are ready for 3.3.2 or 3.4
> unless you don't want me to. Let's get everyone's runtimes and so on ready
> (including mine!) and then call 3.4 the final 3.x release other than bug
> fixing until v4 is cooked?
> 
> Then we can discuss branching etc for v4 - I think we don't need it, we
> just need labels.
> 
> Jim
> 
>> -----Original Message-----
>> From: antlr-dev-boun...@antlr.org [mailto:antlr-dev-boun...@antlr.org]
>> On Behalf Of Terence Parr
>> Sent: Monday, March 07, 2011 5:57 PM
>> To: antlr-dev@antlr.org Dev
>> Subject: Re: [antlr-dev] moving to ST v4 for ANTLR v4 release this year
>> 
>> i created antlr4.dev branch spec to get
>> 
>> code/antlr/dev/antlr4.dev/...
>> 
>> subdir in depot.  Should we all use this as the "mainline" branch for
>> v4 dev?
>> 
>> I will explain my plans for v4 soon but basically it will *not* be a
>> complete rewrite as I thought.  I'm upgrading v3 codebase, hence,
>> branch from main line.
>> 
>> Ter
>> 
>> On Mar 7, 2011, at 5:30 PM, Terence Parr wrote:
>> 
>>> Hi,
>>> 
>>> took no time at all to emit code using STv4 not ST v4.  Those targets
>> with ST port should consider the changes.  STv4 will be out in a few
>> weeks.  In a dev branch, we can start building a 4.0 release.
>>> 
>>> 
>> http://www.antlr.org/wiki/display/ANTLR3/Converting+the+ANTLR+v3+runtim
>> e+to+use+ST+v4+instead+of+ST+v3
>>> 
>>> Ter
>>> _______________________________________________
>>> antlr-dev mailing list
>>> antlr-dev@antlr.org
>>> http://www.antlr.org/mailman/listinfo/antlr-dev
>> 
>> _______________________________________________
>> antlr-dev mailing list
>> antlr-dev@antlr.org
>> http://www.antlr.org/mailman/listinfo/antlr-dev

_______________________________________________
antlr-dev mailing list
antlr-dev@antlr.org
http://www.antlr.org/mailman/listinfo/antlr-dev

Reply via email to