[development] pointreleases and guidelines for contribs

Bèr Kessels ber at webschuur.com
Fri Jul 14 18:43:44 UTC 2006

Hello there.

Frustrating: you install a broken/buggy/nonworking module 'released' for 4.7, 
only to find that it was just branched so people could work towards a 

Confusing: You install foo.module develop something against it, then you find 
that after a few weeks there is a whole new (incompatible) foo.module, still 
with the 4.7 tag. 

Slowing down:   You have loads of spare time (or more likely: a client/project 
that requires lots of improvements to your foo.module) ou don't want to wait 
for 4.8 with showing the world All The Cool New Features. You dont want to 
break your stable releases. You only want HEAD to be 

Contribs have no dot releases (its one number, being the core release, nothing 
else). Contribs have no other branches nor tags then these. 

Therefore I would like to know if, other then project.module not being able to 
handle finer-grained releases, there are reasons not to allow 4.7.1 4.7.2 etc 
releases in contribs. 

If none, how much (estimated) time would it take to add this to the packaging 


| Bèr Kessels | webschuur.com | Drupal, Joomla and Ruby on Rails web 
development |
| Jabber & Google Talk: ber at jabber.webschuur.com |
| http://bler.webschuur.com | http://www.webschuur.com |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
Url : http://lists.drupal.org/pipermail/development/attachments/20060714/d33c224a/attachment.pgp

More information about the development mailing list