Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Andreas, > EVS Windermere (a1) Build 2830 (Test Build Sep 24 2007, i686-pc-linux-gnu) > Copyright 2006- Tony Hoyle and March Hare Software Ltd. > using CVSNT technology. > see http://www.evscm.com for details. Great work! Really very well done. > * Testing, testing, testing Is this client and server? Which databases have you configured (eg: just sqlite, or did you get postgres running?). Any chance you were able to find/run the automated tests? Here is the testing list that Glen is currently working through on windows if it is any help (some of it is windows specific)... * sspi protocol only (hereafter referred to as "remote") * run all tests as administrator first, then later as a non-priveleged user of your choice) * remote import * checkout ascii/binary/mix of ascii/binary * add/commit ascii/binary/mix of... * test "cvswrappers" with "add/commit" * modify/commit ascii/bin/ary/mix of... * add/commit utf8/unicode * modify/commit utf8/unicode * cvs rtag -b (branch) -- note this is very different to "tag" now, so early in testing don't try and mix tag's and rtag's * modify/commit on trunk followed by merge on branch (mergepoint merge) * modify/commit on branch followed by merge on trunk (mergepoint merge) * add/commit on trunk followed by merge on branch (mergepoint merge) * add/commit on branch followed by merge on trunk (mergepoint merge) * modify/commit -B on trunk followed by merge on branch (-b mergepoint merge) -- for this to produce any reliable results you'll have to commit several different bug numbers producing several revisions, then try and merge just one of them... * add -b/commit -B on trunk followed by merge on branch (-b mergepoint merge) -- for this to produce any reliable results you'll have to add/commit several different files using several different bug numbers producing several revisions, then try and merge just one of them... * commit with bug id -B * edit * edit with bug id -b, followed by commit with bug id -b * test previously known unicode bugs (4623,4729,4734,4776), reuse the same tests sets where possible * test chacl etc Regards, Arthur