Here is the first stable release of EVS including EVSManager:
http://www.evscm.org/archive/en-cm-se ... trial-x86-3.1.01.3292.msi
and the client here:
http://www.evscm.org/archive/en-cm-mi ... trial-x86-3.1.01.3292.msi

There is currently NO installation guide (the beta guide is out of date) and NO evaluation guide. A dramatically improved EVSManager will be available in February.

The purpose of this milestone was to release a build that is functionally equivalent to CVSNT and (with the odd exception) SVN, plus these features:
* a fast "rtag"
* rename and move
* transactional database (atomic commit and checkout)
* a single windows service evsmanager that provides:
+ CVS/CVSNT port 2401 services
+ CVSNT Lock Service port 2402 services
+ SVN Services
+ use of web folders to create revisions of files in a repository
+ integrated web browsing of the repository

The February release will add the following to evsmanager:
+ VSTS Services
+ integrated defect tracking based on the Bugzilla data model
+ richer user interface with better process support


EVSCM is the first SCM system with support for the open "CVS protocol" that has no file (or RCS) backend but a relational SQL database. This has not been done simply for the "cool" factor - but because it creates a platform that we can build more advanced functionality on in a very robust way.

Please post your comments and bug reports to support.evs on the news.cvsnt.org (nntp/news) server.

We will not be making any additional builds of EVS for several weeks, but each bug posted to the newsgroup will be recorded and Tony will analyse it to make an estimate of the effort to fix. In around 6 weeks we will look at each of these and prioritise them then look at scheduling. Of course if anyone else wants to simply get in and fix stuff we'd be delighted. If you post a bug I will most likely then give you write access to our bugzilla so you can update it and post more bugs. Ditto with submitting patches for EVS.

Note: the source code to EVSManager is not available, and there is a post on the support.evs newsgroup dated 30/Sep/2007 with the subject "EvsManager" explaining this.

EVS beta2 3.1.01 build 3187 was released today Sep 16, 2008.

It has been a long time between releases, however this one is very significant and indicates that we are (finally) approaching the release of stable.

This is the second build of EVS that includes a preview of the EVSManager, and is the first that contains support for SVN clients. Please remember that this is a beta build and that CVS, CVSNT and SVN clients are not fully supported.

Please read the installation document carefully, it includes:
- known limitations
- installation procedure
- project notes
- the testing we have performed

The document can be downloaded here:
http://www.evscm.org/archive/Installing_EVS.pdf

I have tested this install on a clean server and client and all works - so this build may not be stable, but you should not hit any showstopper bugs that prevent you testing it. The windows installers the server is here:
http://www.evscm.org/archive/evs-server-win32-3.1.01.3187.msi
and the client here:
http://www.evscm.org/archive/evs-client-win32-3.1.01.3187.msi

In particular we are looking for your assistance with:
* migrating the codebase to linux (checkout the trunk from cvs.cvsnt.org), use the postgres driver.
* testing CVS import/add/update/update(merge)/checkout/commit and all acl functions
* testing SVN checkout/commit
* testing rename/move
* testing rtag/tag tag/branch
* testing WebDAV

The purpose of this milestone was to release a build that is functionally equivalent to CVSNT and (with the odd exception) SVN, plus these features:
* a fast "rtag"
* rename and move
* transactional database (atomic commit and checkout)
* a single windows service evsmanager that provides:
+ CVS/CVSNT port 2401 services
+ CVSNT Lock Service port 2402 services
+ SVN Services
+ use of web folders to create revisions of files in a repository
+ integrated defect tracking based on the Bugzilla data model
+ integrated web browsing of the repository

EVSCM is the first SCM system with support for the open "CVS protocol" that has no file (or RCS) backend but a relational SQL database. This has not been done simply for the "cool" factor - but because it creates a platform that we can build more advanced functionality on in a very robust way.

Please post your comments and bug reports to support.evs on the news.cvsnt.org (nntp/news) server.

We will not be making any additional builds of EVS for several weeks, but each bug posted to the newsgroup will be recorded and Tony will analyse it to make an estimate of the effort to fix. In around 4 weeks we will look at each of these and prioritise them then look at scheduling. Of course if anyone else wants to simply get in and fix stuff we'd be delighted. If you post a bug I will most likely then give you write access to our bugzilla so you can update it and post more bugs. Ditto with submitting patches for EVS.

Note: the source code to EVSManager is not available, and there is a post on the support.evs newsgroup dated 30/Sep/2007 with the subject "EvsManager" explaining this.

EVS beta 3.1.01 build 2882 was released today Nov 15, 2007.

This is the first build of EVS that "really" attempts to show what is so great about EVS, because it includes a preview of the EVSManager.

Please read the installation document carefully - it lists known limitations and the installation procedure. The testing we have performed was based on the setup shown in this document:
http://www.evscm.org/archive/Installing_EVS.pdf

I have tested this install on a clean server and client and all works - so this build may not be stable, but you should not hit any showstopper bugs that prevent you testing it. The windows installers the server is here:
http://www.evscm.org/archive/evs-server-win32-3.1.01.2882-beta.msi
and the client here:
http://www.evscm.org/archive/evs-client-win32-3.1.01.2882-beta.msi

In particular we are looking for your assistance with:
* migrating the codebase to linux (checkout the trunk from cvs.cvsnt.org), use the postgres driver.
* testing import/add/update/update(merge)/checkout/commit and all acl functions
* testing rename/move
* testing rtag/tag (tag or branch)
* testing EVSmanager

The purpose of this milestone was to release a build that (with the odd exception) is functionally equivalent to CVSNT, plus these features:
* a fast "rtag"
* rename and move
* transactional database (atomic commit and checkout)
* an evsmanager application that demonstrates how to use EVS as a CM platform, showing:
+ use of web folders to create revisions of files in a repository
+ integrated defect tracking based on the Bugzilla data model
+ integrated web browsing of the repository

This is the first SCM system with support for the open "CVS protocol" that has no file (or RCS) backend but a relational SQL database. This has not been done simply for the "cool" factor - but because it creates a platform that we can build more advanced functionality on in a very robust way.

Please post your comments and bug reports to support.evs on the news.cvsnt.org (nntp/news) server.

We will not be making any additional builds of EVS for several weeks, but each bug posted to the newsgroup will be recorded and Tony will analyse it to make an estimate of the effort to fix. In around 4 weeks we will look at each of these and prioritise them then look at scheduling. Of course if anyone else wants to simply get in and fix stuff we'd be delighted. If you post a bug I will most likely then give you write access to our bugzilla so you can update it and post more bugs. Ditto with submitting patches for EVS.

Note: the source code to EVSManager is not available, and there is a post on the support.evs newsgroup dated 30/Sep/2007 with the subject "EvsManager" explaining this. There will probably be new EVS installers posted with updated EvsManager servers in the coming weeks showcasing additional features (though as noted above the actual EVS server and client will remain unchanged).

Here it is - EVS beta 3.1.01 build 2795 !

Please read the installation document carefully - it lists known limitations and the installation procedure. The testing we have performed was based on the setup shown in this document:
http://www.evscm.org/archive/Installing_EVS.pdf

EVS beta: 3.1.01 build 2795 installation has been tested on a clean server and client and all works - so this build may not be stable, but you should not hit any showstopper bugs that prevent you testing it. The windows installers the server is here:
http://www.evscm.org/archive/evs-server-win32-3.1.01.2795.msi
and the client here:
http://www.evscm.org/archive/evs-client-win32-3.1.01.2795.msi

In particular we are looking for your assistance with:
* migrating the codebase to linux (checkout the trunk from cvs.cvsnt.org), use the postgres driver.
* testing import/add/update/update(merge)/checkout/commit and all acl functions
* testing rename/move

The purpose of this milestone was to release a build that (with the odd exception) is functionally equivalent to CVSNT, plus these features:
* a fast "rtag"
* rename and move
* transactional database (atomic commit and checkout)

This is the first release of a CVS compatible server that has the RCS backend completely removed and replaced by an SQL relational database. This has not been done simply for the "cool" factor - but because it creates a
platform that we can build more advanced functionality on in a very robust way. We are hoping to release to the public a demo Tony created back in February of what can be done with this platform in the coming weeks, however it needs to be updated, stabilised and documented first.

Please post your comments and testing notes to support.evs on the news.cvsnt.org (nntp/news) server.

Additional builds will not be made for several weeks, but each bug will be recorded and Tony will analyse it to make an estimate of the effort to fix. In around 4 weeks we will look at each of these and prioritise them then look at scheduling. Of course if anyone else wants to simply get in and fix stuff we'd be delighted. If you post a bug I will most likely then give you write access to our bugzilla so you can update it and post more bugs. Ditto with submitting patches for EVS.

Latest test build. Currently a Work In Progress but most things work fine.

Changes:

Rename is per-file rather than per-directory, which makes things a lot easier to understand.

cvs prop command to add/remove properties from the file (like admin -p but versioned). Properties are exported into entries.xml on checkout.

Lots of internal reorganisation for speed and reliability. Still some bottlenecks there - will need to work on that.

Tested on vista. WMFree doesn't work correctly due to an apparent bug in the OS (one of the interfaces doesn't work as documented or how it worked in all other OS versions). I need to isolate this to find the cause and/or get a fix from MS.

Build scripts updated so they use SFU if it's there (won't affect most people).

Update -i to support reverse mergepoint usage.

Evs test build 2519.

Changes:

On Unix local mode auto-translate the parameters to utf8.
Obey CVS/Entries directory status (not sure if this is a good idea because I've seen corruption of this quite regularly).
CVS/Repository overrides any calculated idea of the file position.

The first public test build of evs has arrived!

This build is in use on the public repository, and has undergone a fair amount of testing.. however it is likely it still has a couple of glitches so please report anything that you find on the mailing list.

Please test this build as much as possible, in as many configurations as you can.

Known limitations at the moment:

1. Only support for sqlite as a repository database (this is fine for testing).
2. modules2 is not currently working.