[development] Slow down with the official releases of contrib already, ok? ; )

Darrel O'Pry darrel.opry at gmail.com
Thu May 22 20:33:26 UTC 2008

> I think I'm more offended by update status in core, than people creating
>> releases. :)
> Them's fightin' words! ;)

No, it's a statement that code and process is easier to change than people
and my conviction that processes should adhere to people not the other way
around. Not fighting words, just my opinion.

 I'd be really happy to see update_status disabled in core by default

You're obviously not a member of the security team.

I don't think the security of every drupal site is the security teams
responsibility as long as there is a notification system in place.. IIRC
there is an email list and an RSS feed for security notices as well so the
security team is being responsible in its role update_status or no. Taken in
light of my following comment, which you so ingenously separated, makes your
implication that I'm not concerned about security hollow.

 or be made less noisy ie) only make noise on sec update...

Already a knob for this.

Where? Can I control it as a module maintainer?

> Frankly contrib dev is noisy, and I don't see that changing.

I'm not (yet) ready to give up my multi-year quest to bring enlightenment
> about release management to the Drupal project as a whole.  Help in this
> crusade is appreciated.  Nay sayers will be ... ;)

I don't think you should give up. I for one have learned a lot about version
control thanks to your efforts. I think we do have to face 2 facts:

 1) there is a lot to learn and some people won't learn it quickly.
 2) there will always be new people.

Which means contrib will always be noisy, no matter how successful you are
in your self appointed task.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20080522/2155f746/attachment-0001.htm 

More information about the development mailing list