CVSNT
Developer(s)March Hare Software, Ltd.
Stable release
2.5.05 / March 26, 2010 (2010-03-26)
Operating systemWindows, Unix-like, Linux, Mac OS X, OS/400
PlatformCross-platform
TypeRevision control
LicenseGPL
Websitecvsnt.org
CVS Suite
Developer(s)March Hare Software, Ltd.
Stable release
2008 / December 1, 2008 (2008-12-01)
Preview release
2009 / April 16, 2010 (2010-04-16)
Operating systemUnix-like, Linux, Windows, Mac OS X, OS/400
PlatformCross-platform
TypeRevision control
LicenseGPL and others
Websitemarch-hare.com/cvsnt/
EVS (CVSNT 3.1.01)
Developer(s)March Hare Software, Ltd.
Stable release
3.1.01 / December 31, 2008 (2008-12-31)
Operating systemUnix-like, Linux, Windows, Mac OS X
PlatformCross-platform
TypeRevision control
LicenseLGPL
Websiteevscm.org

The CVSNT Versioning System implements a version control system: it keeps track of all changes in a set of files, typically the implementation of a software project, and allows several (potentially geographically separated) developers to collaborate. It is compatible with and originally based on Concurrent Versions System (CVS), which has become popular in the open-source world.

Features

edit

CVSNT keeps track of the version history of a project (or set of files).

CVSNT is based on the same client–server architecture as the Concurrent Versions System: a server stores the current version(s) of the project and its history, and clients connect to the server in order to check-out a complete copy of the project, work on this copy and then later check-in their changes. A server may be a caching or proxy server (a read only server that passes on write requests to another server) or a read and write (normal) server.

Typically, client and server connect over a WAN or Internet, but client and server may both run on the same LAN or even the same machine. The server software runs equally well on Unix and Windows. It is compatible with CVS clients and supports a large number of configuration management methodologies including the CVS compatible unreserved method and the VSS-like reserved method.

The modular nature of CVSNT allows server administrators to dynamically enable and disable protocols as well as load additional functions via triggers such as Audit, Defect Tracking Integration, Automatic Checkout (for webservers) and more.

CVSNT Server features include:

  • Access control for securing projects and branches.
  • Detailed audit and metrics recorded in an SQL database.
  • Authentication with Active Directory.
  • Tracking everything about the change - including whether it was merged from somewhere, belongs to a problem report or was part of a change set.
  • A control panel to manage email notification of changes, defect tracking integration, and more.
  • Integrated repository synchronisation (for fail-over servers).
  • Change set support (group changes by defect number).
  • Supports Unicode UTF-8/UCS-2 files and multi-lingual filenames.
  • When operating in UTF-8 (Unicode) mode it can automatically translate filename encoding for any client.
  • Plug-ins for email notification.
  • Helps make merging branches easier with its "Mergepoint" feature.
  • Native servers available for Mac OS X, Windows, Linux, Solaris, HP-UX.
  • Supports reserved and unreserved versioning methodologies.
  • CVSAPI for integration into third-party products.
  • Script, COM and 3GL interface for triggers and integration into 3rd party tools (such as defect tracking)

History and status

edit

Users unhappy with the limitations of CVS 1.10.8 began the development of CVSNT. The original limitations addressed were related to running CVS server on Windows and handling filenames for case-insensitive platforms.

The first version was released in 1998, and stable feature releases have been released roughly every three to four months since. Linux and Unix support was re-added to CVSNT in early 2002.

From the project's inception until October 2002 CVSNT and CVS used identical version numbers and CVSNT was "kept in sync" with the features and code base of CVS. After October 2002, CVSNT began its own version sequence beginning with "2" to indicate significant departure from its CVS origins. Since that time, there has not been a stable feature release of CVS. However the unstable CVS 1.12 contains some of the oldest features originally implemented in CVSNT. Due to this shared history, all features from CVS 1.11 and most from 1.12 are included in CVSNT.

In 2003, the CVSNT SJIS project released a Japanese version of CVSNT including support for SJIS filenames and file encoding.

March Hare Software began sponsorship of the project in July 2004 to guarantee the project's future and to employ the original project manager on CVSNT development and commercial support.

In February 2005, the project servers moved to CVSNT version 2.5 and began unstable releases of a new server incorporating server plugins, ACLs, filename character set conversion as well as client/server autodiscovery. In October 2005, the first commercial CVS Suite was released, incorporating non-GPL addins and clients for CVSNT. In November 2005, CVSNT was enhanced to incorporate the features of the CVSNT SJIS project.

In March 2006, the project servers moved to CVSNT version 2.6 and began unstable releases of the new server backend. This backend incorporated a partial SQL database repository to facilitate better server performance and more complex server features. When work was abandoned on CVSNT 2.6 and moved o EVS/CVSNT 3.1 the project server was moved back to 2.5.04.

In November 2008 the project released version 2.5.04 with support for multi site repository replication or 'local' repository caches and specific performance features for using large files use over a WAN. The project began advertising for contributors more aggressively including placing advertising in commit comments (which can be turned off).

In March 2010 the project released version 2.5.05 with a server that always runs in Unicode, native Windows crypt and schannel support and support for Internationalized Domain Names.

The open source CVSNT project does not have a "project charter". This was a decision based on the observation that the charter prevented the CVS project from evolving CVS into a versioning system supporting modern CM best practice. The CVSNT project will continue to evolve the software as the scope of version management and CM changes, including changes to expand the supported methodologies.

The status of the project is active, with further releases of CVSNT 2.5 planned, and continuing evolution of CVSNT/EVS 3.1. CVSNT/EVS will implement a complete SQL database repository to support further complex server and client features. An RCS emulation layer is also planned for CVSNT/EVS 3.1 to support legacy systems.

Community Edition

edit


On June 30th, 2010[1], March Hare retired the zero-dollar Community edition, however the commercial "CVS Suite" edition with a new CVSNT 2.8 release and support is actively developed[2] and available from the web store[3], as are snapshots of the older community releases (unsupported, and a fee is required to download) [4]. Email support is available for customers but the community mailing list/newsgroup has been removed,

This decision has been criticised by several different people for differing reasons.

Reason 1: It was free and now it is not

edit

Despite the Free Software Foundation[5] and various CVSNT developers attempting to explain the difference between Zero-dollar software and Free Software, there is extensive criticism of March Hare Software's decision to change CVSNT from 'free' to 'paid'[6].

Users of CVSNT publicly claimed that given a business case that they could support the project financially[7] and the vendor claims this is a part of the reason they switched to a paid-but-still-free model.

Reason 2: availability of the source code

edit

The description of the public CVS server for source code was updated with the caveat "not guaranteed to be available 24x7[8], is provided by a volunteer and may be withdrawn at any time"[9]. People have claimed [citation needed]</ref> that this arrangement is a violation of the GPL, It is probably insufficient to simply cite the GPLv2 Section 3[10] since a quick reading by does not suggest there is any obligation for the vendor to ensure that the download source is available 24x7.

People have also claimed that trial versions of the software are offered for download but do not come with the source code, or a written offer to receive the source code, which is explicitly required by the license[11], but this is refuted by counter claims by the vendor that CVS Suite 2009 Trial does install a link to the vendors web site with detailed information about how to obtain the source code [12].


Reason 3: it was better before

edit

Future roadmap

edit

March Hare plans to deliver the following features in the next release "CVSNT/EVS 3.1.01". Retrieved 2007-12-04. :

See also

edit
edit

Literature

edit

References

edit
  1. ^ "EVS Developer Support Downloads: Announcement". EVS Open Source Website. Retrieved 1 July 2010.
  2. ^ "what integrates better - CVS or Mercurial?". Bugzilla/Mozilla Project. Retrieved 7 December 2010.
  3. ^ "Buy CVSNT Versioning Solutions". March Hare Software. Retrieved 1 July 2010.
  4. ^ "Unsupported Community Software". March Hare Software. Retrieved 1 July 2010.
  5. ^ "The Free Software Definition". Retrieved Feb 2011. {{cite web}}: Check date values in: |accessdate= (help)
  6. ^ "CVSNT: a failure of the open source model?". February 2011.
  7. ^ "March-Hare message into my commit messages". Retrieved Feb 2011. {{cite web}}: Check date values in: |accessdate= (help)
  8. ^ "What is the CVS Suite License". March Hare Software. Retrieved 13 Feb 2011.
  9. ^ "CVSNT is Changing". March Hare Software. Retrieved 13 Feb 2011.
  10. ^ "GNU General Public License, version 2". The Free Software Foundation. Retrieved 13 Feb 2011.
  11. ^ "GNU General Public License, version 2". The Free Software Foundation. Retrieved 13 Feb 2011.
  12. ^ "What is the CVS Suite License?". Retrieved 13 Feb 2011. {{cite web}}: Text "publisherMarch Hare Software" ignored (help)