Plan to move asm to trunk

So it looks like most development has moved to the asm branch, and
that the asm branch has probably reached "good enough" to become
trunk.  Still, I want to check and make sure that this is the right
thing to do.

My plan for this move would look something like this:

1) Announce a freeze of trunk
2) make a Release_2_3maint branch against the current trunk, and a
Release_2_3a0 tag to mark the last of the javacc based Jythons -- just
in case someone needs to continue with that  (say a GSOC student that
still needs this version, or someone in the future that cannot use
ANTLR for some reason...)
3) merge asm into trunk using svnmerge.py
4) soon after release a proper alpha2 with a proper Release_2_5maint
branch, a proper tag, etc -- which would have been difficult for
alpha1 because I made it from a branch and not trunk.

I think that's it...

Thoughts?

-Frank

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/