Truth, I just won't do it. I'm rather release a new module and retire the old one come version shift time.<br><br>I develop modules for my use, and return them to the Drupal community because, well, I just do. But I don't do feature request for free because
<br>1- it will never end<br>2- I'd have to find out which version a person is using to <br><br>And yes, schema and feature complete is the earliest I'll ever tag a project. I may refactor the code after bug fix requests settle down
<br><br><div><span class="gmail_quote">On 2/3/06, <b class="gmail_sendername">Jeff Eaton</b> &lt;<a href="mailto:jeff@viapositiva.net">jeff@viapositiva.net</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
That raises a question for me, though -- what happens if I want to<br>release a major new version of my module in three months, after 4.7 has<br>shipped? Should I start using one set of tags for the drupal version and<br>
another for the module 'milestone' version?<br></blockquote></div><br>