[cvsnt] Corrupt history file
arthur.barrett at march-hare.com
Tue Nov 21 07:59:23 GMT 2006
>>Tony, it would be really helpful if you could post a message to a
>>thread pointing to a bug/request when you have fixed it. As it is now
>>we have to just check again in the next release to see if it was
>A proper bug/issue tracker would be better...
As previously mentioned - Tony no longer works much on the CVSNT code, and the bug tracker is here:
There are two ways to get something fixed:
1) Report bugs to this newsgroup, once it is tested/verified on the current testing release by one of the seniors on the group then it should be reported by them (with suitable testset and trace to cvsnt-dev. From there Glen or I can add it to the bug database and it'll get scheduled according to severity/priority.
2) check out the code from the repository and fix it yourself (by far the quickest way). Submit the patch to cvsnt-dev and Tony, Glen or Myself will review and commit it. If you look trustworthy (eg: have submitted one reasonable patch) then we'll be happy to grant you checkin rights and also write access to tt (the bugzilla database) and the wiki.
The previous technique used by Tony to manage development was more efficient for the intesive changes taking place, however that has now all moved to the EVSCM project. Consequently there is a transition period where things may get lost.
The only confirmed bugs in CVSNT 2.5.04 testing build I'm aware of are in tt.
There are also a few bugs in tt that are obviously already fixed and will get cleaned up in the 2.5.04 release process (eg: 4678, 4573), as well as some that I have patches for but not in the tree (eg: 4713). There are also a bunch of patches related to the commercial features in 2.5.04 that I'm currently getting into shape for commit - as they are committed I (currently) intend on creating bugs for them.
Oh and the tt interface to Bugzilla shouldn't be showing the Tortoise and other "suite only" bugs - that should be easy to fix....
More information about the cvsnt