Hey guys, this is an Open Source project (or was the last time I checked).<br><br>So, releases get done when they are ready.<br><br>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.<br>
<br>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.<br>
<br>saludos,<br><br>Victor Kane<br><a href="http://awebfactory.com.ar">http://awebfactory.com.ar</a><br><br><div class="gmail_quote">On Feb 18, 2008 8:20 AM, Ashraf Amayreh <<a href="mailto:mistknight@gmail.com">mistknight@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">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.<br>
<br>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.<div><div></div><div class="Wj3C7c">
<br>
<br><div class="gmail_quote">On Feb 18, 2008 11:43 AM, Xavier Bestel <<a href="mailto:xavier.bestel@free.fr" target="_blank">xavier.bestel@free.fr</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br><br>I'm writing a little rant about modules. I know it's tempting when you<br>start your module to call it a "development version", because it doesn't<br>work so well yet or it's not finished. But many modules never leave that<br>
state, and e.g. now that the official Drupal version is 6.x and that<br>version 5.x is just a bugfix release, there are still many modules with<br>only a 5.x-1.x-dev release.<br><br>There's also the case where you have a concurrent -dev and numbered<br>
release, but only the -dev release has the features and the bugfix to<br>make it usable.<br><br>This isn't just a cosmetic problem. As all releases have the same name,<br>it's very inconvenient to store different versions, e.g. to go back in<br>
case of problem. Also it doesn't work so well with the update module<br>(even if it tries to workaround that).<br><br>So please, do proper releases. If you need to work on features, do a<br>parallel 1.n and 2.n version, but avoid using -dev in code which should<br>
really be used.<br><br>Thanks,<br><br> Xav<br><br><br></blockquote></div><br><br clear="all"><br></div></div><font color="#888888">-- <br>Ashraf Amayreh<br><a href="http://blogs.aamayreh.org" target="_blank">http://blogs.aamayreh.org</a>
</font></blockquote></div><br>