[development] Changes to CVS tagging/branching conventions for contrib (MUST READ)
drupal at dwwright.net
Tue Jul 31 21:19:46 UTC 2007
1) Starting with Drupal 6.x, branches in the contributions CVS
repository will always contain the --N part of the branch name, to
remind people that each release series belongs in its own branch.
You can now create a DRUPAL-6--1 branch for the 6.x-1.* release
series for your contributions. There will never be a DRUPAL-6 branch
in the contributions repository (the repository itself prevents it).
If you're Jeff Eaton and you already have 2 versions of your D6
modules ready ;) the 6.x-2.* code belongs in HEAD or in the
DRUPAL-6--2 branch (also now open), not in DRUPAL-6--1. This change
is only for DRUPAL-6--1 and beyond, the DRUPAL-5 branches in contrib
2) If you make "beta" or "rc" releases, the "extra" part of your tag
can only contain upper case letters and numbers (no lowercase,
hyphens, underscores, etc). So, these are valid:
These are not:
Old tags that don't follow these rules will continue to exist.
However, new tags, even for DRUPAL-5--*, will be disallowed if they
don't match the new convention.
More info about why I made these changes are here:
Discussion is now closed, but these contain a lot of good wisdom and
motivation. If you have any doubts, please read these issues
carefully and your concerns will almost certainly be addressed and
The following handbook pages are updated to reflect the new reality:
I also updated the Contributed modules status - version 6.x wiki on
If you happen to find another CVS handbook that has stale info,
please either fix it yourself if you can, or create a documentation
issue about it if you can't. Otherwise...
Happy D6 porting!
p.s. Did I mention that this email is about changes that already
happened which are no longer up for debate? This is not an RFC or
proposal soliciting feedback. If you reply to this thread with "why
did you do that?" or "I liked it better the old way..." you'll make a
certain CVS admin very unhappy... and bad things happen when you do
that. ;) If you think you don't like either of these changes, read
the issues I point to above very carefully. If you still think these
changes are a mistake, please find someone else to complain to, since
a) you're wrong and b) I don't want to have to tell you that again. ;)
More information about the development