There's nothing wrong with Drupal's versioning system. If you used the KDE &quot;standard&quot; you'd be around version 16 or so by now.<br><br>But most people expect what Steven suggested so people are misled by their expectations...and they have no real reason to expect something else.
<br><br>You DON'T have to change it. You DO have to expect the same confusion every version change as the user (NOT the developer) community grows.<br><br>Not that there hasn't been enough discussion and plans laid to cover every complaint made in the last few days. You ARE addressing upgrades through the install system. There's been discussion of core vs verified vs &quot;Wild West&quot; contributions. You're working on install profiles, which will also be maintained via 
update.php, I guess. <br><br>What else...being nice to end users? Does anyone REALLY need advice on how that's done?<br><br>That's my biweekly contribution to non-coding subjects.<br><br><div><span class="gmail_quote">On 5/31/06, 
<b class="gmail_sendername">Steven Peck</b> &lt;<a href="mailto:speck@blkmtn.org">speck@blkmtn.org</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;">
<br>There are other projects that use different from KDE versioning release<br>scheme's as well.&nbsp;&nbsp;Drupal's been consistent for the 3 years I've used it<br>with it's versioning information and method.&nbsp;&nbsp;The versioning scheme has
<br>not changed at all.<br><br>-sp<br></blockquote></div><br>