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 email@example.com.
Hello list, Bo Berglund <bo.berglund at telia.com> writes: > >CVSNT Server: 2.5.02 (Servalan) Build 2064 > > Too old version, this was in the middle of development flow and there > are several other issues with versions close to this one. > Update the server to build 2151 or later to get a safer system. How could this build get the stable tag then? I tend to do updates very rarely since I noticed that many stable versions are later withdrawn their stability. It seems to me that only pro-customers and very close observers know what version is best to use. How do you handle this? If I use todays stable version im not sure if it's really stable or shows problems when installed on a larger base. But the previous stable versions are all still marked as stable, even if they showed problems in the field. Even the bugzilla db does not give me the information. For version 2.5.02.* I find 27 entries, but 17 of them are closed before 2064. Only two are fixed later, the rest is still open. So the _real_ problems seem to live outside of the bugzilla... Btw. the buglist does not contain any mention of modules2, which is often reported to be only partly working on this list. Rename is also not part of the open-bugs-list. On a closer look one might find even more open points not mentioned in the bug-db. I don't want to complain, I'm happy with cvsnt as it does a great job. I'm only feeling helpless if it comes to the updates. It always needs a lot of testing before one can use a new version. The only point of reference is this mailing list, but this does not give you a quick overview on the state of versions. Maybe we need more feedback on positive test results. The list often contains reports of issues but no feedback from the reporter or others if the fixed version does the trick. And the bugzilla only contains the information that the problem has been worked on, but not that it's fixed and works in all cases. Sorry for taking this thread over. I don't know how to explain it in more detail. I just wanted to trigger some thoughts about the cvsnt release policy. Thanks for listening, O. Koltermann Disclaimer: This is meant as constructional criticism.