Howdy,

So, the main branch is now the focal point for v4. I have branched off of the 
main line just now to create an antlr3-main branch. From this, we can release a 
3.3.1 or 3.4 version if we need to before v4 is done. So, as of this moment, 
any changes you put in the mainline are headed only for v4. If you want it to 
go into v3 possibly, then please edit that branch. You have permissions now for 
this branch.

        write user jluber * //depot/code/antlr/antlr3-main/...
        write user sharwell * //depot/code/antlr/antlr3-main/...
        write user matthewl * //depot/code/antlr/antlr3-main/...
        write user jimi * //depot/code/antlr/antlr3-main/...
        write user jhurst * //depot/code/antlr/antlr3-main/...
        write user KyleYetter * //depot/code/antlr/antlr3-main/...
        write user acondit * //depot/code/antlr/antlr3-main/...

Here's the diagram again to help out

<<inline: branching.gif>>


If you sync, you will see a whole bunch of stuff come across and the root 
directory will be called antlr3-main and live at the same level as just plain 
main. :)

I will now go pull all of my antlr4.dev changes back into main and obliterate 
it. :)

This means that I should probably change the nightly build to a different 
branch ;) I guess I can keep the 4.0 branch up there.  Jim, so should I make 
pom.xml 4.0-SNAPSHOT in the mainline?

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

Reply via email to