[JCL] developer repository migration

2006-03-28 03:13:31 AM
Hi everyone,
The Jedi Code Library will change its developer repository.
Presently, developers and users can access the latest source using CVS
(Concurrent Version System). The anonymous access to the CVS repository
has been running with poor quality of service for the past few months
and JCL users could hardly update their repository.
In February, Sourceforge released to all projects a new system to
control their source named subversion (also named SVN).
This version control system has many advantages over CVS and some new
functionalities that will help further development (this comparison is
developed in the Subversion book that can be freely read at
All active developers of the Jedi Code Library are ok to migrate to this
system. This migration was announced few weeks ago in the developer
forums (news://forums.talkto.net:119/jedi.jcl).
As you have probably noticed in the JCL homepage on Sourceforge
(sourceforge.net/projects/jcl), the “subversion?tab appeared,
this page contains information to connect to the SVN repository and to
browse its content from a web browser.
Starting from April 1st 2006 (this is not a joke), the latest sources of
the JCL will only be present in the SVN repository, the CVS repository
will be kept read-only for courtesy purposes, changes made in the SVN
repository after this migration date will NOT be replicated into the CVS
All users that want to have an access to the latest source will have to
use subversion. For Windows users, TortoiseSVN
(tortoisesvn.sourceforge.net/) is a shell integration that is as
easy to use as TortoiseCVS.
The daily zips of the JCL developer repository, that can be downloaded
from jcl.sourceforge.net/daily/, will now contain a snapshot of
the subversion repository updated every day.
The Jedi Visual Component Library (JVCL homepage
jvcl.sourceforge.net) should migrate to subversion in short time.
More details will be given in the JVCL developer forum
Florent Ouchet
JCL Team Coordinator