update notification service

[gormus]

We increased our drush usage on all drupal projects. When drush pm-update command is used to update a Pressflow instance, it would update it Drupal vanilla, rather than the latest Pressflow release.

I looked into Drush code and documantation and also the Pressflow code changes. Apparently Drush's behavior is normal, since it checks the update status via installed Drupal/Pressflow instance's update.module

Honestly I was expecting Pressflow would patch update.module with Pressflow's update notification service URL for the core, and the default for the contributed modules and themes. So that Drush would work as expected and update Pressflow, rather than replacing it with Drupal vanilla.

Is there any plan for near future to make this kind of of a change? Or is it against Drupal policies?

Thanks,

Osman

[gormus]

Here are my initial finding:

1. Pressflow needs to maintain a release-history URL which would be used in updating Pressflow, just like Drupal's own:
   http://updates.drupal.org/release-history/drupal/6.x
2. Version info should be restored in .info files. version = VERSION will not help.
3. Add following line to each .info files
   project status url = 'http://updates.pressflow.org/release-history/pressflow/6.x'
version = 6.24

I think 'UPDATE_DEFAULT_URL' constant in update.module should not be changed, since Drupal maintained release history keeps all projects' version history.

References from api.drupal.org
_update_get_fetch_url_base

UPDATE_DEFAULT_URL

_update_build_fetch_url

I would like to know what do you think about this, and what we can do to bring automatic updates to Pressflow.

Cheers,
Osman