[development] death to "x.y.z" version is now inevitable

Derek Wright drupal at dwwright.net
Thu Nov 16 10:37:42 UTC 2006

On Nov 15, 2006, at 6:10 PM, Darrel O'Pry wrote:

> in case I confused anyone else...

please stop spreading confusion. ;)

> DRUPAL-4-7--1 is DRUPAL-4-7 and is a branch...

again, please read this thread to understand why not:

> DRUPAL-4-7--1-0 is a release tag in the DRUPAL-4-7/DRUPAL-4-7--1
> branch...

just call it "the DRUPAL-4-7" branch, since that's what it is.   
talking about "DRUPAL-4-7--1" as if it exists will do nothing but  
confuse people...

> DRUPAL-4-7--2 is another branch.
> DRUPAL-4-7--2-0 is a release tag within the DRUPAL-4-7--2 branch....


> and .x is the laymans term for a dev version...

'x' is a variable, like high-school algebra.  it's a place-holder for  
something you don't know the value of. ;)  if it's the '.x' right  
before a '-dev', then yeah, it just means "you don't know the patch  
level, since you just have something from the end of a branch, not a  
specific tag.".  if it's the '.x' in the first part of the version  
(e.g. 4.7.x-1.0), it means "any version of core with the version  
4.7.something".  as in, "this module is compatible with 4.7.1, 4.7.2,  
4.7.3, etc.  in this case, there's nothing particularly "dev" about  
it.  so, equating ".x" with "dev" is misleading.

to avoid potential problems using '*' for this (can't have '*' in the  
name of the tarball, for example), and since my goal was as much  
uniformity of the identifiers as possible, i figured people could  
handle using 'x' as an unknown value.


More information about the development mailing list