Derek, (and Tao, Chad and Adam),<br><br>You are the heroes of the community. This is a crucial part of the ecosystem<br>and you are improving it to continue to be the centerpiece of contribs.<br><br>I take off my turban for you ...<br>
<br><div class="gmail_quote">On Thu, Mar 6, 2008 at 2:38 AM, Derek Wright <<a href="mailto:drupal@dwwright.net">drupal@dwwright.net</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;">
If you own any project nodes on d.o please read this...<br>
<br>
I just finished up a patch[1] that was holding up a string of<br>
improvements to project nodes. The most important new functionality<br>
is that you now have more fine grained control over what releases are<br>
displayed on your project nodes[2].<br>
<br>
First of all, for each version of core, you now have separate<br>
controls for every major version, where you can specify if that core/<br>
major combination is supported, and if you want a dev snapshot<br>
displayed for it or not. Then, if you've got multiple major versions<br>
for the same version of core, you get a radio to select which version<br>
is recommended.<br>
<br>
Update status (both in D6 core and D5 contrib) already knows about<br>
all of this, it just hasn't been visible on d.o yet. So, previously,<br>
when you changed the "recommended version", update status would<br>
immediately warn users they should upgrade, which caused much<br>
confusion and hassle. Now, update status will only warn users to<br>
upgrade once you uncheck the "supported" checkbox. So, you can have<br>
both 5.x-2.* and 5.x-1.* supported, and 5.x-2.* recommended, and<br>
update status won't bother people still running 5.x-1.*. However,<br>
say you ship a 5.x-3.*, and decide to drop support for 5.x-1.*, you<br>
can uncheck the box and update status will tell them to upgrade.<br>
<br>
Now, all it means when you mark a given major version "recommended"<br>
is a) it's displayed as such on the project nodes, b) update status<br>
says so in its status report, and c) it's the version that'll be<br>
shown in the project teaser in the project browsing pages.<br>
<br>
Furthermore, recommended releases are now colored green on the<br>
project nodes and project browsing pages, whereas -dev snapshots are<br>
always marked as red (to warn people not to download them for real<br>
sites).<br>
<br>
I also fixed a caching bug where sometimes the release tables would<br>
have "edit" links in them which most users would get permission<br>
denied on, while other tables wouldn't have edit links for users who<br>
could use them.<br>
<br>
Finally, I fixed a wonky bug that would require visiting and saving<br>
the "releases" subtab of the edit tab on your project node whenever<br>
you added a new release for a whole new version of core.<br>
<br>
Enjoy,<br>
-Derek (dww)<br>
<br>
p.s. Thanks to Tao (starbow) for some of the cool jQuery goodness on<br>
that new edit/releases UI.<br>
<br>
p.p.s. Thanks to Chad (hunmonk) and Adam (aclight) for reviewing and<br>
testing this stuff.<br>
<br>
[1] <a href="http://drupal.org/node/176776" target="_blank">http://drupal.org/node/176776</a><br>
[2] <a href="http://drupal.org/node/203313" target="_blank">http://drupal.org/node/203313</a><br>
<br>
<br>
<br>
</blockquote></div><br><br clear="all"><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.