[development] code names for core releases?

Earl Miles merlin at logrus.com
Wed Sep 20 00:06:55 UTC 2006

Derek Wright wrote:
> <goes even further out on a limb>
> in fact, maybe the best solution is to just ditch that concept and go  
> to "major.patch" version numbers for core. ;)  we could just call the  
> next version "5.0", the security releases and bug fix releases "5.X",  
> and we know the next version of core will become "6.0".  we'd always  
> know what the next version will be -- they just monotonically  
> increase.  so what if in 5 years, we're up to version "15.0" or  
> something?  it's not like we're going to run out of bits in the  
> integers that hold these values anytime soon. ;)
> </back to reality>

Actually, I agree with this even more. I hate Drupal's current version 
numbering system.

More information about the development mailing list