Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

jonasbn (1153)

jonasbn
  reversethis-{gro.napc} {ta} {nbsanoj}
http://e-diot.dk/
AOL IM: BJonasN (Add Buddy, Send Message)

Perl Programmer located in Copenhagen, Denmark. Active member of Copenhagen Perl Mongers.

Author of:

  • Business::DK::CPR
  • Business::DK::CVR
  • Business::DK::PO
  • Business::OnlinePayment::CashCow
  • Date::Holidays
  • Date::Holidays::Abstract
  • Date::Holidays::Super
  • Date::Pregnancy
  • Games::Bingo
  • Games::Bingo::Bot
  • Games::Bingo::Print
  • Module::Info::File
  • Module::Template::Setup
  • Test::Timer

and maintainer of:

  • Tie::Tools
  • XML::Conf
  • Workflow

Journal of jonasbn (1153)

Tuesday June 05, 2007
04:36 AM

Workflow moving from CVS to SVN

[ #33432 ]

I have just completed the process of migrating the CPAN module 'Workflow' from CVS to Subversion. The project is hosted on SourceForge in order to open up for easier community development and open source activities.

SourceForge offers both CVS and SVN. We (the developers) decided however to move to Subversion.

I have had some problems getting cvs2svn to work on my MacBook Pro, but this here tip helped me out and I have converted the CVS repository to a dump, which has been imported into subversion.

Until now everything has worked out fine and the documentation from SourceForge is actually quite good. I would love it to include a different layout though and perhaps a step by step guide, instead of just a collection of prose.

The CVS repository will be disabled after I have evaluated that everything works as expected.

At the same time I have written up the road map for Workflow as a HTML document. This still requires some work, but I am attempting to get all the things in place so we can pick up on the development.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.