Great Idea
rubenk - December 21, 2006 - 08:11
I am probably not the first one to think of this but
why not have a "my modules" section that shows recent updates only of the modules that a user has downloaded either by allowing a user to specify which modules he/ she uses (e.g. radio buttons) or asking the user to login before downloading a module to track which ones have been downloaded or a combination of both methods.
It would Save me a lot of sifting especially if I could signup for email updates of new releases of my branch (ie. 5.0) of the modules I use or get an RSS feed or even just see it as an option on the modules page.
Anyone else find this useful?
If so, perhaps a formal feature request is in order.

There was some talk about
There was some talk about the new module release system being able to to things like this. Checkout the latest podcast at lullabot.com - you might find that someone else is thinking along the same lines
I'll cheek it out.
I'll cheek it out.
you're on The money
Cheek it out! :)
that's the product of using a tablet pc.
the site is here
http://www.lullabot.com/audiocast/drupal_podcast_no_28_derek_wright_and_...
CVS :)
If I'm following the development of anything, I check it out via CVS, rather then downloading the tarball.
I put all contributed modules into a
contributionsdirectory under modules - either under root or sites.Anytime I feel like it I can just cd to that directory and
CVS update- or use the built-in cvs support of my environment - right-click winCVS or Eclipse. to update any directory just like that.my notes on howto do this
.dan.
How to troubleshoot Drupal | http://www.coders.co.nz/
I thought about this but I
I thought about this but I like "stable" fully baked releases
Something feels funny about using CVS on a production site
so say so
add
-r DRUPAL-4-7to lock your checkout into only the tagged stable versions..dan.
How to troubleshoot Drupal | http://www.coders.co.nz/
you can get a specific release tag from CVS, too
you can also do this:
cd contributions/modules/foocvs update -r DRUPAL-4-7--1-2
if you want the 4.7.x-1.2 release of a specific module ("foo", in this case).
these already exist as "formal" feature requests. ;)
http://drupal.org/node/94137 ("email subscriptions for release nodes")
http://drupal.org/node/94138 ("RSS feeds for release nodes")
http://drupal.org/node/94154 ("module page could say if new releases are available")
cheers,
-derek