<br><br><div class="gmail_quote">On Fri, May 30, 2008 at 10:23 AM, Larry Garfield <<a href="mailto:larry@garfieldtech.com">larry@garfieldtech.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;">
<div class="Ih2E3d"><br></div>
One of the issues with -dev is that some module maintainers use it for "mostly stable but I've not fully debugged it yet, please test", while others use it for "dude, it doesn't even compile, it's got syntax errors all over the place, wtf are you using it for?" And there's no way to tell which is which, and it can even change over time in the same module.<br>
<br>
What if we allowed non-pattern-compliant branches, but did not permit the creation of release nodes? That would allow those with more CVS-fu to do all kinds of wacky "me only" experimental branches but people who still get all their code from <a href="http://drupal.org/projects/*" target="_blank">drupal.org/projects/*</a> won't even have a way to get to it until it goes into the "main, kinda stable, needs testing" -dev branch (which module maintainers don't even have to make release nodes for if they don't want to, as now).<br>
<font color="#888888"></font></blockquote><div><br>I can't speak for the more experienced maintainers, but this sounds complicated and over my head. :) My devs tend to fall somewhere in the middle of those two extremes and I simply document that on the project page. Maybe we should just encourage people to put a note on their pages saying how _they_ feel about the state of their dev snapshots so potential users can decide which they'd rather use?<br>
<br>Michelle<br><br></div></div><br>