[development] Module developers, please do *proper* releases !

Victor Kane victorkane at gmail.com
Mon Feb 18 10:28:21 UTC 2008

Hey guys, this is an Open Source project (or was the last time I checked).

So, releases get done when they are ready.

It's really up to each module developer to decide when a stable release
should be ready, since use is always on an "as is" basis.

Obviously there may be irritating cases where there is a chronic "dev"
release that "everyone uses"; but that has to be handled on a case by case
basis, and usually via a good natured mail to the maintainer.


Victor Kane

On Feb 18, 2008 8:20 AM, Ashraf Amayreh <mistknight at gmail.com> wrote:

> Sometime I think this should become a requirement rather than something
> optional, all current dev releases could be promoted to a first release and
> new dev releases banned.
> Not sure how good an idea this is, but if dev releases are so unstable,
> then maybe they should remain unreleased until they are, and if they are
> stable, then there's no reason for them to be dev.
> On Feb 18, 2008 11:43 AM, Xavier Bestel <xavier.bestel at free.fr> wrote:
> > Hi,
> >
> > I'm writing a little rant about modules. I know it's tempting when you
> > start your module to call it a "development version", because it doesn't
> > work so well yet or it's not finished. But many modules never leave that
> > state, and e.g. now that the official Drupal version is 6.x and that
> > version 5.x is just a bugfix release, there are still many modules with
> > only a 5.x-1.x-dev release.
> >
> > There's also the case where you have a concurrent -dev and numbered
> > release, but only the -dev release has the features and the bugfix to
> > make it usable.
> >
> > This isn't just a cosmetic problem. As all releases have the same name,
> > it's very inconvenient to store different versions, e.g. to go back in
> > case of problem. Also it doesn't work so well with the update module
> > (even if it tries to workaround that).
> >
> > So please, do proper releases. If you need to work on features, do a
> > parallel 1.n and 2.n version, but avoid using -dev in code which should
> > really be used.
> >
> > Thanks,
> >
> >        Xav
> >
> >
> >
> --
> Ashraf Amayreh
> http://blogs.aamayreh.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20080218/6c226d71/attachment-0001.htm 

More information about the development mailing list