Branch module for 4.7

i'd like to get more of the critical and annoying bugs fixed before we do, just so we don't have to incur the cost of having to commit everything to 2 or 3 branches instead of just 1 or 2. personally, i say -1 until a few more of the existing issues are closed. not the end of the world either way, but i'd personally hold off.

if the goal was to get a 4.7 release out there, perhaps we should just add a non-branch DRUPAL-4-7 tag (which we might move a few times) to hold us over until we're happier with the HEAD.

-derek

bump. ;) i think i've changed my mind on this. aside from the fact that it's not the end of the world to commit to 2 branches instead of 1, there's a new issue that can't be fixed until we make the branch: http://drupal.org/node/64352 is a new bug from something that's in core's HEAD, but not DRUPAL-4-7. so, we should only commit the fix to that into HEAD once there's safely a DRUPAL-4-7 branch of project. so, i withdraw my earlier -1 and convert to a +1.

shall i pull the trigger? ;)

killes applied my patch that fixed the cvs access control scripts. i wanted to test tagging and this seemed like the perfect candidate. ;) DRUPAL-4-7 branch now exists.