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.
One thing I would like to add on this, as I'm one of those not quite willing to upgrade just yet :-), is that TortoiseCVS is currently shipping 51d and not 58d. Since we make extensive use of cvs acl's and those changed between these versions, we are sticking to pre 58d. I've always thought that the 'noise' level about a release on this list was a very good indicator as to how safe a new version has been :-) The noise about 58d has been going down steadily lately, so I'm hoping that the issues with that release have been worked through. But I'm not considering upgrading until TortoiseCVS updates, so I have a consistent chacl command. I'm afraid most of my users get pale when I mention the command line, so I'm dependent on TortoiseCVS (as I suspect many are) and not necessarily where CVSNT is at. Fortunately, my main cvs server (2.0.41a) is rock solid, and my hot spare (2.0.51b) is too, so I don't have any pressing need to upgrade. Thanks, John Cole -----Original Message----- From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf Of Oliver Giesen Sent: Thursday, November 18, 2004 7:34 AM To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: [cvsnt] Re: CVSNT & File Permissions Tony Hoyle wrote: > Hartmut Honisch wrote: > > I recommend CVSNT 2.0.51d - it was marked as stable, and it works > > for me - 2.0.58 (the current stable release) had some problems. > > There isn't much wrong with 2.0.58d (nothing showstopper, anyway). Unfortunately, apart from your continually stating this, this is not really the impression I get from following the discussions here. Add to that the fact that AFAICT changes between 2.0.51d and 2.0.58 were quite more fundamental than in earlier releases... E.g. the scrapping of old-style fileattr and replacing it with something XML-based - not that I think that was a bad thing to do as such - very much to the contrary - but this is very unlike most of the other fundamental stuff you've added so far, like binary and compressed deltas, custom encodings, atomic commits, the lockserver or renames. All of those had to be used very consciously before they became effective. Sometimes they even had to be explicitly enabled first. If I wasn't interested in one of those features yet, there was still no harm in upgrading to a version that supported them as upgrading alone did not irreversibly change anything in my repository unless I explicitly started to use those features. If a release turned out to be buggered down the line I was still able to just go back to last version before that (unless I had chosen to use those features already). Now, AFAIHU fileattr gets (re)written as soon as I add or import files or even just do something as simple as Edit, so there's pretty much no way to delay "using" this new feature until it's proven ultimately stable. In this case, this effectively renders my repository no longer backward compatible to older versions of the server. So, in case any more serious issues crop up with the release (the potential is always there as you will have to admit) I will no longer be able to go back to an earlier release. That is probably the main reason why I am so reluctant to upgrade this time and why, like Hartmut, I still recommend 2.0.51d to people. As it is now I will probably wait for at least one more "stable" release and then some before I upgrade again. And that even though up to 2.0.51d I pretty much always upgraded on the spot as soon as you posted your "Latest Updates" message... :( Or is my assessment utterly incorrect here? Have you left open a "downgrade path" for the fileattr stuff? Another factor which strengthens this sentiment is that there *do* appear to be an increased number of reports about permissions and other problems (however minor) with post-2.0.51d builds recently... And I don't even want to start about the more minor/emotional/irrational gripes I have with the recent builds, like turning "HEAD" into a branch and adding exclusive edits... > I > don't recommend using an older release as it's harder to support. Perfectly understood. Another reason why I'm not at all happy with the current situation (see other thread about problems with 2.0.51d). Still trying to keep the faith... Cheers, -- Oliver ---- ------------------ JID: ogiesen at jabber.org ICQ: 18777742 (http://wwp.icq.com/18777742) _______________________________________________ cvsnt mailing list cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs ------------------------------------- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.