Plan for moving asm to trunk part deux

Even more than the last time I suggested this, most development has
moved to the asm branch, and the asm branch has probably reached
"good enough" to become trunk.  Philip Jenvey pointed out some
problems that have since been resolved.  I still want to check and make
sure that this is the right thing to do.

My plan for this move is the same as before:

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
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...

-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=/