I only wanted to point at http://sourceforge.net/projects/cvsphpview, which may help getting cvs data for the modules.

Comments

douggreen’s picture

douggreen commented

Thanks for the reference! I'm actually using http instead of CVS to pull the information, so using something that used cvs would definitely be cleaner. However the consensus of Drupal Developers is to move away from CVS and towards the new Drupal project release system.

With the Drupal 6 code freeze is about 3 months away, I' am trying to limit the new features and CVS integration for releasemonitor and work towards a significantly rewrite aimed at Drupal core.

ray007’s picture

ray007 commented

Yeah, I know it's using http to the viewcvs system of drupal, thought that could make life easier.

New project release system? Didn't know about that.
What are they going to use instead of cvs? Whatever they use for project management, we still need version control too.

douggreen’s picture

douggreen commented

I'm referring to what's already in place now on d.o and the D5 info files:

New system for releasing Drupal contributions
New release system for Drupal contributions now deployed!

There are more references if you search the Drupal Developer list archives. If you want to help, you could search the archives for threads related to version2, releasemonitor, auto-install, project release system, and others.

douggreen’s picture

douggreen commented
Title: CVS access » Getting versions using CVS / the new project release system
Category: task » feature
Priority: Minor » Normal
douggreen’s picture

douggreen commented
Status: Active » Closed (won't fix)

The future of this module is uncertain, mainly because of the update_status module, so I'm not planning on any updates in the near future.