On Sat, Feb 23, 2008 at 1:11 AM, Dries Buytaert &lt;<a href="mailto:dries.buytaert@gmail.com">dries.buytaert@gmail.com</a>&gt; wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Also, why the &#39;by the community&#39; part? &nbsp;Why not just &#39;reviewed and<br>
tested&#39;? &nbsp;Please rename at least to &#39;reviewed and tested&#39;. &nbsp;Everything<br>
we do is community-driven so &#39;by the community&#39; is completely<br>
redundant. &nbsp;It seems to &nbsp;suggest that there is a non-community body as<br>
well.<br></blockquote></div><br>Dries, <br><br clear="all">The reason is backward compatibility for the acronym, so that newcomers<br>would check old issues and see &quot;RTBC&quot; and the new words would match it<br>same with the old words.<br>
<br>Personally, we break backward compatibility all the time in Drupal, and<br>saw what the heck, it is worth it. So why not do the same with issue status<br>and documentation too? Yeah, some inconvenience for sure, but better in<br>
the long term.<br>-- <br>Khalid M. Baheyeldin<br><a href="http://2bits.com">2bits.com</a>, Inc.<br><a href="http://2bits.com">http://2bits.com</a><br>Drupal optimization, development, customization and consulting.