[cvsnt] EVS beta: 3.1.01 build 2795

[Arthur Barrett]

Hi all,

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

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.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.

I know Tony really wanted to be the one to announce all this, but it took me 
longer to test than I expected and he is on a well deserved break this week. 
He will be excited to see your comments and testing notes on his return. 
Please post them to support.evs on the news.cvsnt.org (nntp/news) server.

We will not be making any additional builds 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.

Regards,


Arthur Barrett