<br><br><div class="gmail_quote">On Thu, Mar 5, 2009 at 1:16 PM, Matt Farina <span dir="ltr"><<a href="mailto:matt@mattfarina.com">matt@mattfarina.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On the documentation side of updating there is <a href="http://drupal.org/" target="_blank">http://drupal.org/</a>update. If you are talking about modules see <a href="http://drupal.org/update/modules" target="_blank">http://drupal.org/update/modules</a>.<br>
<br>
Also note that, a number of module maintainers (for widely used projects) have openly said they would like to release versions of their modules when drupal 7 is released.</blockquote><div><br><div id="result_box" dir="ltr">
Indeed,
the contrary, I believe that it is stable API that can make a valuable
in enterprise environments. (SDL, DirectX, Carbon, Cocoa etc ...). <br>
<br> We should begin to put these arguments on the table, backward and 'a subject that will' sooner or later be addressed.</div><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Dries, also, said that releasing drupal 6 without <a href="http://drupal.org" target="_blank">drupal.org</a> being updated to it was a mistake he doesn't want to see happen again.</blockquote><div><br>Why it's happen ? Because big missing, "Views, OG, Panels etc...etc...", because backward compatibility API doesn't exists. <br>
<br>Could be possible have a more abstract API on top of new features, decoupling the implementation from the interface.<br><br>P.<br></div></div><br>-- <br>Paolo Mainardi<br><br>Vice Presidente Assoc.ILDN (<a href="http://www.ildn.net">http://www.ildn.net</a>)<br>
Blog: <a href="http://www.paolomainardi.com">http://www.paolomainardi.com</a><br>