Hi List, Is there a set of rules or best practices for how to deal with module releases and branches? Best regards, Eric
Try: http://drupal.org/handbook/cvs and http://drupal.org/handbook/cvs/quickstart On Wed, Dec 1, 2010 at 10:03 AM, Eric Schaefer <eric.schaefer@eas-consulting.de> wrote:
Hi List,
Is there a set of rules or best practices for how to deal with module releases and branches?
Best regards, Eric
This has quite a bit of info: http://drupal.org/handbook/cvs/branches-and-tags -- psynaptic http://twitter.com/psynaptic http://drupalcontrib.org/ On 1 Dec 2010, at 15:03, Eric Schaefer wrote:
Hi List,
Is there a set of rules or best practices for how to deal with module releases and branches?
Best regards, Eric
Oh, sure: http://drupal.org/node/93999 Gábor On Wed, Dec 1, 2010 at 4:03 PM, Eric Schaefer <eric.schaefer@eas-consulting.de> wrote:
Hi List,
Is there a set of rules or best practices for how to deal with module releases and branches?
Best regards, Eric
2010/12/1 Gábor Hojtsy <gabor@hojtsy.hu>:
Oh, sure: http://drupal.org/node/93999
That's exactly what I was looking for. Thanks, Eric
I'll just take this opportunity to note: once the git migration is completed, branch/tag naming & restrictions will work quite differently. There'll be no restrictions on what branch/tag names you can send into your project repositories (like the ones on the page Gabor linked to). So, great for collaboration, feature branches, and all other sorts of things that git makes easier. There will, however, be restrictions on what branches/tags you can use to make official releases. However, instead of it being the arcane system described at #93999, it'll quite closely resemble the human-readable branch names and tag names we're accustomed to seeing. Generally, they'll follow this convention: Branches: 'DRUPAL-6--1' becomes '6.x-1.x' Tags: 'DRUPAL-6--1-0-ALPHA1' becomes '6.x-1.0-alpha1' 'DRUPAL-6--2-2' becomes '6.x-2.2' Much saner :) On 12/1/10 9:52 PM, Eric Schaefer wrote:
2010/12/1 Gábor Hojtsy <gabor@hojtsy.hu>:
Oh, sure: http://drupal.org/node/93999
That's exactly what I was looking for.
Thanks, Eric
Sam Boyer wrote:
Branches: 'DRUPAL-6--1' becomes '6.x-1.x'
Tags: 'DRUPAL-6--1-0-ALPHA1' becomes '6.x-1.0-alpha1' 'DRUPAL-6--2-2' becomes '6.x-2.2'
Much saner :)
I wouldn't say "saner", just easier to type. It is the project module that provided the need for branching and tagging the way it is defined today. It will be the changes to the project module that defines the way branching and tagging is defined tomorrow. -- Earnie -- http://progw.com -- http://www.for-my-kids.com
participants (6)
-
Earnie Boyd -
Eric Schaefer -
Gábor Hojtsy -
Richard Burford -
Sam Boyer -
Steve Karsch