On 1/31/07, Robert Garrigós Castro <robert@garrigos.cat> wrote:
Shouldn't have been drupal 5.1 named 5.0.1?
Please see http://drupal.org/handbook/version-info#core -- e www.eafarris.com
On 31-Jan-07, at 11:56 AM, Robert Garrigós Castro wrote:
Shouldn't have been drupal 5.1 named 5.0.1?
I wouldn't like to start (again?) a (previous?) discussion, but, when no number appears, anywhere in the world, in any field, a zero is understood. Which means, drupal 5 could have been named 5.0.0.0.0.0.0. This page it selfs (http://drupal.org/node/93998) talks on a drupal 5.0 beta. The add project release form shows three fields for major, minor and patch-level numbers. This 5.1 is a new patched drupal, right? It should be 5.0.1, IMHO.
No. This has been discussed and discussed and discussed. Drupal 4.7.x and below uses the first two digits to indicate the major version, the third to indicate the patch version. This confused the living hell out of people, who perceive that 4.6.x to 4.7.x is a 'minor' update. Drupal 5.x and above will be using the first digit for the major version, and the second digit to indicate the patch version. It would be silly to call it 5.0.x because we would never have a 5.1. The next version of Drupal will be called 6.x, and the one after that is 7.x. No more confusion. http://drupal.org/handbook/version-info has way more info than you'd ever want to know on this topic. -Angie
On Wed, 2007-01-31 at 18:01 -0500, Angela Byron wrote:
Drupal 5.x and above will be using the first digit for the major version, and the second digit to indicate the patch version. It would be silly to call it 5.0.x because we would never have a 5.1. The next version of Drupal will be called 6.x, and the one after that is 7.x. No more confusion.
a big light goes on in dopry's head and the shadows of confusion are banished.
On Jan 31, 2007, at 3:17 PM, Robert Garrigós Castro wrote:
What confused me was that the Release Project module doesn't work like this. It actually uses the t[h]ree version numbers system.
project.module has to support a ton of different styles of version numbers, since it's used by: a) old versions of core (4.7.6) b) new versions of core (5.1) c) old versions of contrib (4.6.0) d) new versions of contrib for old versions of core (4.7.x-1.3) e) new versions of contrib for new versions of core (5.x-1.2) just be thankful it works at all. ;) 'nuff said, -derek
I think Robert's asking about the "releasemonitor" module. Robert created the "version" module which did some simple things related to CVS versions. I contacted him when I was developing "releasemonitor". "releasemonitor" was a first attempt by find programmatically discover which modules were ready for D5 and which modules had D47 updates. I've only been coding for Drupal for less than a year, so it's bound to not "know" the "Drupal" way of doing things. I hope to update it in the coming months, fix it for php4, and have a broader discussion about what and how it should do things. Dries asked if I'd help contribute this for D6, which I said yes to. Doug Green www.douggreenconsulting.com www.civicactions.com Changing the world one node at a time! -----Original Message----- From: development-bounces@drupal.org [mailto:development-bounces@drupal.org] On Behalf Of Derek Wright Sent: Wednesday, January 31, 2007 6:32 PM To: development@drupal.org Subject: Re: [development] drupal 5.1 or 5.0.1 On Jan 31, 2007, at 3:17 PM, Robert Garrigós Castro wrote:
What confused me was that the Release Project module doesn't work like this. It actually uses the t[h]ree version numbers system.
project.module has to support a ton of different styles of version numbers, since it's used by: a) old versions of core (4.7.6) b) new versions of core (5.1) c) old versions of contrib (4.6.0) d) new versions of contrib for old versions of core (4.7.x-1.3) e) new versions of contrib for new versions of core (5.x-1.2) just be thankful it works at all. ;) 'nuff said, -derek
participants (6)
-
Angela Byron -
Darrel O'Pry -
Derek Wright -
Doug Green -
eric Farris -
Robert Garrigós Castro