[development] Consolidating duplicate contrib modules for D7

Ken Winters kwinters at coalmarch.com
Wed Dec 9 03:14:21 UTC 2009

On Dec 8, 2009, at 9:41 PM, Daniel F. Kudwien wrote:

>> How exactly do you define 'release to the public'? Commiting
>> code to a development branch used only by developers? Or
>> releasing ready-made quality-inspected module packages?
> Almost all projects have development snapshot releases that are  
> repackaged
> every 12 hours.  How much more is "public"?

Exposed to the general public rather than just developers, that is.   
Everyone can download any branch
of the code regardless, but the recommended releases need to be more  

When someone creates a release node, everyone with update status  
enabled and an older
version of the module will know about it, and the implication is that  
they should update.  Ill-
advised release creation has caused a lot of grief to a lot of people  
in the past, so this process
should not be taken lightly.  Breaking the devel branch is one thing,  
but breaking the "stable" branch
and broadcasting is far more disruptive and hardly inspires confidence  
in the module / CMS.

- Ken Winters

More information about the development mailing list