[development] New functionality on project nodes installed on d.o

Derek Wright drupal at dwwright.net
Thu Mar 6 07:38:02 UTC 2008

If you own any project nodes on d.o please read this...

I just finished up a patch[1] that was holding up a string of  
improvements to project nodes.  The most important new functionality  
is that you now have more fine grained control over what releases are  
displayed on your project nodes[2].

First of all, for each version of core, you now have separate  
controls for every major version, where you can specify if that core/ 
major combination is supported, and if you want a dev snapshot  
displayed for it or not.  Then, if you've got multiple major versions  
for the same version of core, you get a radio to select which version  
is recommended.

Update status (both in D6 core and D5 contrib) already knows about  
all of this, it just hasn't been visible on d.o yet.  So, previously,  
when you changed the "recommended version", update status would  
immediately warn users they should upgrade, which caused much  
confusion and hassle.  Now, update status will only warn users to  
upgrade once you uncheck the "supported" checkbox.  So, you can have  
both 5.x-2.* and 5.x-1.* supported, and 5.x-2.* recommended, and  
update status won't bother people still running 5.x-1.*.  However,  
say you ship a 5.x-3.*, and decide to drop support for 5.x-1.*, you  
can uncheck the box and update status will tell them to upgrade.

Now, all it means when you mark a given major version "recommended"  
is a) it's displayed as such on the project nodes, b) update status  
says so in its status report, and c) it's the version that'll be  
shown in the project teaser in the project browsing pages.

Furthermore, recommended releases are now colored green on the  
project nodes and project browsing pages, whereas -dev snapshots are  
always marked as red (to warn people not to download them for real  

I also fixed a caching bug where sometimes the release tables would  
have "edit" links in them which most users would get permission  
denied on, while other tables wouldn't have edit links for users who  
could use them.

Finally, I fixed a wonky bug that would require visiting and saving  
the "releases" subtab of the edit tab on your project node whenever  
you added a new release for a whole new version of core.

-Derek (dww)

p.s. Thanks to Tao (starbow) for some of the cool jQuery goodness on  
that new edit/releases UI.

p.p.s. Thanks to Chad (hunmonk) and Adam (aclight) for reviewing and  
testing this stuff.

[1] http://drupal.org/node/176776
[2] http://drupal.org/node/203313

More information about the development mailing list