Posted by Merlin on Tue Jan 30, 2007 11:25 pm.
We're almost there with this. Only a few more days, hopefully. I'm so excited I can hardly stand it -- this is the planned destination of a crusade I've been on for several months now.
(I doubt the final product will look like this, but it's certainly a good start)

| Attachment | Size |
|---|---|
| updater.png | 18.66 KB |


I would like this feature
I would like this feature also.
Wonderful
A very important feature. I also think (despite of the problems), that there should also be an autoupdate feature indicated per module, as well as an "update all modules now". Some modules' updates I 'trust' completely (views being one of them), and some I just want the latest updates on the test site.
I certainly agree that there
I certainly agree that there should be some kind of auto update. Figuring out how to do this properly and safely is of course a trick, but we'll come up with something.
Ideally I want things to be as easy as it is for those who want to type 'cvs update -dP' and then hit update.php and be done with it.
I think it should still be kicked off and monitored by an administrator. I'd never be comfortable with it fully automated.
This is fantastic!!
While I agree that a (safe) auto upload is the final goal, just this reporting module is a HUGE step forward! Thanks for taking the time! Your work is primo and much appreciated (now, can you build a better forum?) :-)
Which version(s) of Drupal will this module work with?
Looks great! This is going to be extreamly helpful
Is there any chance that releases that fix security bugs will be flagged as such? This would be an important feature and distinction IMO.
Nice work!
we <3 angry donut
as any teenage girl would text it on a cell
-
was wondering why there inst a feed somewhere that listed all the moduls & the version number.. But with this we dont ned no stinkin feed :P
/mdk
RSS for Modules
http://drupal.org/taxonomy/term/78/0 is the rss feed for 5.0 compatible modules...
Seeing the status of drupal and contrib stuff that you are using in your site is awesome ...
Such a module will add a lot
Such a module will add a lot of value into the Drupal community.
Will it work with 4.7?
There has already been a
There has already been a significant amount of work done on this - no need to start something new!
Check it out: http://drupal.org/project/releasemonitor
Right now project module isn't providing easily machine readable output (RSS is not enough really), so releasemonitor uses CVS to detect module updates. It can detect updates on the current branch (your basic updates), as well as updates on the next major branch (so it can tell you when all the modules you are using have Drupal 5 versions available).
Release Monitor came along
Release Monitor came along well after this project was underway. The author basically ignored those of us who were working with Drupal to get this stuff in and did his own thing. That's all well and good but if you want to accuse someone of starting something new, go accuse that guy. I've had my sights on this end goal ever since I first started work on the Modules page (that was completely redone by others for Drupal 5, I'll add).
It's just that we've been working on the server angle, because CVS is a really, really poor way to keep track of what state your code is in. CVS is for development.
What you're seeing above is just a module in Nedjo's sandbox that's being used to test the system. It's quite small.
releasemonitor sounds fine,
releasemonitor sounds fine, but unfortunately doesn't work with php4
Just queries how the
Just queries how the development is going!
Any updates?
Any updates?
differences between module_status module and the releasemonitor?
looks like an interesting module but since there is another module has a similar function (releasemonitor module) i wonder what are the real differences between module_status module and the releasemonitor module?
differences between module_status module and the releasemonitor?
interesting module but since there is another module has a similar function (releasemonitor module) i wonder what are the real differences between module_status module and the releasemonitor module?
This feature will be much
This feature will be much appreciated Merlin.
Post new comment