[BioPython] Biopython to migrate to Subversion

Chris Lasher chris.lasher at gmail.com
Sat Mar 24 16:35:04 UTC 2007


Hello Biopythonistas,

The Biopython developers are currently planning a migration from CVS
to Subversion as our revision control system. The target for the
migration is the evening of Sunday May 20, 2007. This change will
mostly impact the developers, however, this may also affect some
users.

If you're a user of Biopython and you...

A) install Biopython from the Windows installer, from packages for
your Linux distribution, or from Fink on OS X...

you will not be affected. You may stop here or read on at your own leisure.

-----

B) download and install from the source in the form of the Tarball or
Zip file...

you will not be affected. You may stop here or read on at your own leisure.

-----

C) retrieve and install Biopython from the CVS repository...

the Biopython devs would really like to hear from you!

For those in category C, the change could mean that you will need a
Subversion client installed on your computer. Clients exists for all
major platforms, including Windows, OS X, and Linux.

Subversion operates through HTTP/HTTPS (ports 80 and 443,
respectively), and specifically uses WebDAV, an extended HTTP
protocol. Though highly unusual, some organizations networks' may
block WebDAV traffic. One way to check whether your organization does
this is to attempt to checkout an existing Subversion repository from,
for instance, a Google Code Project (all of which use Subversion
repositories). For example, you can attempt to check out Kongulo
<http://code.google.com/p/google-kongulo/source>. If you can checkout
an existing repository, you will be ready to migrate to Biopython's
Subversion repository once in place.

If Subversion installation will not be possible, or your network
indeed blocks WebDAV traffic, the Biopython devs need to know. We can
support the CVS repository with read-only access and inject updates
from the Subversion repository into the CVS repository. This involves
a bit more work on the part of devs in setting up and supporting, so
we will take this on only if the necessity exists.

For clarity, Biopython will make a clean move to Subversion and drop
CVS support unless we hear requests for legacy CVS support in advance
of the migration.

-----

If you're a developer of Biopython...
you should be on the Biopython-dev list and have been following this
thread: <http://tinyurl.com/2jd8om>

-----

We will document all things related to Biopython's migration to
Subversion on the Biopython wiki at
<http://biopython.org/wiki/Subversion_migration> for interested
parties.

The developers look forward to a smooth transition and having
Subversion in place to assist us in continually improving Biopython.

Thank you for your time and feedback,
Your friendly neighborhood Biopython developers



More information about the Biopython mailing list