DRUPAL-5-0 tag/branch available
Hello, this is to let you know that I added the 'DRUPAL-5-0' tag/branch to the set of available tags/branches. This means that you can branch your contributed projects if you want to. Your project won't be packaged until we make the first beta release available. -- Dries Buytaert :: http://www.buytaert.net/
On Thursday 14 September 2006 10:54, Dries Buytaert wrote:
this is to let you know that I added the 'DRUPAL-5-0' tag/branch to the set of available tags/branches. This means that you can branch your contributed projects if you want to. Your project won't be packaged until we make the first beta release available.
Dries, In your mind, does tagging a module for 5.0 imply that the module is 100% ready for production, or only that it is functional to the point of not causing any fatal errors or breaking the overall system? I guess I'm looking for guidelines on how far along a module should be before being tagged for 5.0, given that Drupal core itself is a moving target right now, and core changes might break a module that previously worked with HEAD. Comments? Scott -- ------------------------------------------------------------------------------- Syscrusher (Scott Courtney) Drupal page: http://drupal.org/user/9184 syscrusher at 4th dot com Home page: http://4th.com/
In your mind, does tagging a module for 5.0 imply that the module is 100% ready for production, or only that it is functional to the point of not causing any fatal errors or breaking the overall system?
I guess I'm looking for guidelines on how far along a module should be before being tagged for 5.0, given that Drupal core itself is a moving target right now, and core changes might break a module that previously worked with HEAD.
You asked Dries, but here's my opinion... ;) A module without a 5.0 tag does not tell an end user anything. It could be bleeding edge, but it could also be an outdated module. There is no way for them to know. If you are making an effort to maintain your module, then you should definitely tag it. If an end-user downloads a module tagged as 5.0, but it does not work, then they know that they can expect an update in the future. If it's not tagged as HEAD, they are left in the dark. Late tagging IMO slow down the release of Drupal core 4.7.0 before: too many contributed modules were not tagged, causing too many people to stick to 4.6. In spite of us releasing several betas, it took until the final release candidate for people to really start testing the release and finding some easy to spot bugs. In short: tagging, yes please, as soon as possible. Steven Wittens
Steven Wittens wrote:
In your mind, does tagging a module for 5.0 imply that the module is 100% ready for production, or only that it is functional to the point of not causing any fatal errors or breaking the overall system?
I guess I'm looking for guidelines on how far along a module should be before being tagged for 5.0, given that Drupal core itself is a moving target right now, and core changes might break a module that previously worked with HEAD.
You asked Dries, but here's my opinion... ;)
Same here.
A module without a 5.0 tag does not tell an end user anything. It could be bleeding edge, but it could also be an outdated module. There is no way for them to know.
Well, I'd expect that a module tagged with 5.0 should at least have the basic conversion from 4.7 done. Simply tagging now with the idea of updating when I've got time and interest isn't helping at all. I am not sure you wanted to imply that but I wanted to state my opinion nevertheless.
If you are making an effort to maintain your module, then you should definitely tag it. If an end-user downloads a module tagged as 5.0, but it does not work, then they know that they can expect an update in the future. If it's not tagged as HEAD, they are left in the dark.
I'd be very annoyed if a module is tagged as 5.0 but it doesn't work at all with a current RC. Some glitches are of course to be expected.
Late tagging IMO slow down the release of Drupal core 4.7.0 before: too many contributed modules were not tagged, causing too many people to stick to 4.6. In spite of us releasing several betas, it took until the final release candidate for people to really start testing the release and finding some easy to spot bugs.
Well, 4.7 was different from all the releases we have done before in that it rewrote large parts of a subsystem in a way we hadn't done it before. The change from 4.7 to 5.0 is in many ways more similar to the changes from 4.5 to 4.6.
In short: tagging, yes please, as soon as possible.
But only if you made some effort in converting it... Cheers, Gerhard
On 15 Sep 2006, at 01:54, Steven Wittens wrote:
If you are making an effort to maintain your module, then you should definitely tag it. If an end-user downloads a module tagged as 5.0, but it does not work, then they know that they can expect an update in the future. If it's not tagged as HEAD, they are left in the dark.
A module that is tagged with DRUPAL-5-0 will be made available for download. At that pint, the module _should_ work as expected. Hence, you tag your module when it is ready for production use. Don't tag your module to indicate that you will convert it in future. End-users don't care about that, and it complicates their lives.
In short: tagging, yes please, as soon as possible.
Tag your module as soon it works properly with Drupal 5.0.0. -- Dries Buytaert :: http://www.buytaert.net/
On Friday 15 September 2006 05:53, Dries Buytaert wrote:
In short: tagging, yes please, as soon as possible.
Tag your module as soon it works properly with Drupal 5.0.0.
Fair enough. Thanks to all who replied. Scott -- ------------------------------------------------------------------------------- Syscrusher (Scott Courtney) Drupal page: http://drupal.org/user/9184 syscrusher at 4th dot com Home page: http://4th.com/
participants (4)
-
Dries Buytaert -
Gerhard Killesreiter -
Steven Wittens -
Syscrusher