Today while I was updating my Firefox extensions, it occurred to me that this would be some really nice functionality to have in a CMS. What if every time an admin logged in or ran a "Check For Updates" module, he'd get a list of his active modules with lower version numbers that what's currently available in CVS? Maybe the list has a link to each module's project page for immediate review and download. The module itself sounds like it would be relatively simple: parse the version number out of each of the module files and compare them against a master list of current versions. The trick would be that master list. I'm imagining something like an XML file hosted on cvs.drupal.org that generates on call (or maybe once a day). Does this sound interesting to anyone but me? Is there any way we could extract latest version numbers from CVS? -- Dan Ziemecki Philosopher. Curmudgeon. Nerd.
Dan Ziemecki wrote:
Today while I was updating my Firefox extensions, it occurred to me that this would be some really nice functionality to have in a CMS. What if every time an admin logged in or ran a "Check For Updates" module, he'd get a list of his active modules with lower version numbers that what's currently available in CVS? Maybe the list has a link to each module's project page for immediate review and download.
The module itself sounds like it would be relatively simple: parse the version number out of each of the module files and compare them against a master list of current versions.
Check issues #48580 and #48582 and see if they will give you something close to what you want. We've got a design, we just need to implement it (for 4.8+). ..chrisxj
Yeah! One of those! Ahem. Okay. Can you tell I've been out of the loop a while? Do we really need to wait for 4.8? Seems like we could do something like this *now* if we had the CVS side component. -- Dan Ziemecki On 3/6/06, Chris Johnson <chris@tinpixel.com> wrote:
Dan Ziemecki wrote:
What if every time an admin logged in or ran a "Check For Updates" module, he'd get a list of his active modules with lower version numbers that what's currently available in CVS?
Check issues #48580 and #48582 and see if they will give you something close to what you want. We've got a design, we just need to implement it (for 4.8+).
..chrisxj
Do we really need to wait for 4.8? Seems like we could do something like this *now* if we had the CVS side component.
There is a feature freeze on 4.7 in effect for sometime now. Once this is released, then HEAD will open for features and this can go in provided it passes reviews, ...etc. and be on its way for 4.8 (or 5.0 as the case may be). Alternatively, you can make that a contrib module, then it can be released with 4.7.
I was thinking of this as a contrib module, but core would, of course, be better. I'll keep an eye on the CVS side component and make a call based upon how that goes. -- Dan Ziemecki On 3/6/06, Khalid B <kb@2bits.com> wrote:
Do we really need to wait for 4.8? Seems like we could do something like this *now* if we had the CVS side component.
There is a feature freeze on 4.7 in effect for sometime now.
Alternatively, you can make that a contrib module, then it can be released with 4.7.
participants (3)
-
Chris Johnson -
Dan Ziemecki -
Khalid B