[development] update_status and the new project node functionality

[Omar Abdel-Wahab]

Thank you Derek for the immense effort you're putting in project module.
The new changes, IMO, bridges the gap between what the community wants
(track module versions, choose the right version of a module, etc...)
and what developers need (at least what I think: easy to use release
system).

Omar

On Sat, Mar 8, 2008 at 7:16 PM, Derek Wright <drupal at dwwright.net> wrote:
> Now that you've all had a few days to play with the new toys, I
>  finally pulled the lever to generate the XML files that update_status
>  uses based on the new settings on your project nodes.  So, your
>  changes on those settings are now "live" for the purposes of
>  update_status -- please be cautious and aware of the fact that when
>  you deselect the "supported" checkbox on a given branch, your users
>  will see a nice big red warning about it.
>
>  After I did this, I noticed a few modules (e.g. devel and
>  comment_upload) where giving me warnings since the officially
>  supported versions were 5.x-0.*, but i was running a 5.x-1.x-dev
>  (from CVS).  I fixed up the settings on those two modules, so now
>  both 5.x-0.* and 5.x-1.* are supported, but the official releases
>  from 5.x-0.* are still recommended.  However, other modules that use
>  '0' for the major version should beware, check the node/N/edit/
>  releases tab on your project(s), and configure things
>  appropriately.   This is exactly the kind of edge case that the
>  heuristics I mentioned in a previous message couldn't handle without
>  human intervention.
>
>  Cheers,
>  -Derek (dww)
>
>  p.s. For now, these XML files are only regenerated every 6 hours, so
>  if you alter some project settings, then manually fetch data on the
>  available updates report, you won't immediately see the changes.  I'd
>  like to see that fixed if anyone wants to help.  See:
>  http://drupal.org/node/184418
>
>
>
>