[development] Version2 Module

[Doug Green]

Sure, I'd be happy to work on this next part.  

I do want to point out that my current module helps with the upgrade from
4.7 to 5.0.  If your site installed the contrib modules from CVS (which I
believe will be many/most professional developers), install this new module
on your 4.7 sites, and view the /admin/version page.  

Sorry about the name.  I knew it was bad.  I pretty much developed the
module overnight, and wanted to get it out.  What do people think of
"Project Release Monitor" ("projectreleasemonitor" in cvs)?

I don't think it's as bad as Dries says.  It wasn't a waste of time because
this module will help some people with the 4.7 -> 5.0 upgrade (me being one
of them).  For it to be useful to the Drupal masses, though, it needs to
(and will) use the new project system.

Doug Green
www.douggreenconsulting.com
www.civicactions.com
 
-----Original Message-----
From: development-bounces at drupal.org [mailto:development-bounces at drupal.org]
On Behalf Of Dries Buytaert
Sent: Wednesday, January 03, 2007 2:45 AM
To: development at drupal.org
Subject: Re: [development] Version2 Module


On 03 Jan 2007, at 03:15, Derek Wright wrote:
>> I really, really think using information from CVS for updates is a  
>> bad, bad idea and is a step backward from where we're heading.
>
> i basically agree, but given what actually exists right now, there  
> aren't a lot of better alternatives.  we desperately need a  
> solution (i.e. someone to write the code) for:

While it's a cool little project, I agree with Derek's and Earl's  
assessment.  I hate to say it, but Doug's time was better spent  
implementing http://drupal.org/node/48580. :)  Of course, that can  
still happen, and version 2 of version2 (ugh, what a bad name!) could  
be updated to integrate with project module.  What do you think  
Doug?  We'd love this functionality done right! :-)

--
Dries Buytaert  ::  http://www.buytaert.net/