Conflict?

Exactly my thoughts... I know Merlin writes "the good stuff", but in this case, he's not made it clear *why*.

ReleaseMonitor displays more info (although it needs a fair bit of work) - it's not clear why these modules coexist rather than complement each other?

Release monitor checks the status of your modules through CVS.

It doesn't know anything about the 'official' released versions, meaning you cannot keep your code to just stable versions through releae monitor.

Release monitor can help you keep your development versions up to date.

Release monitor was made into a project well after all the work on update status was in place. The projects are not merged because their methodologies are decidedly different, and for my purposes, release_monitor uses an inferior methodology.

(That said, it *can* track CVS updates for you, which is good for development sites and absolutely terrible for production sites).

I like both of these modules, though update status seems like a much better module - especially in how it is presented.

Its a shame it doesn't track all changes to modules though, as often (especially now with the move to drupal 5) lots of the modules we use have only done dev release to bring them up to date.

Either way - thanks for this.

It is my hope that the existence of the update_status module will convince contrib developers to create releases. There are a LOT of great reasons for this, the primary one being that if code is released it's a lot easier to tell what's going on with a bug report. Simply using a moving -dev target can be a real hassle.

I've got all this covered in a FAQ on the main project page, so I think this issue can be closed.