Hello!
> There are always plans. ;-) Releases really need to be done by
> OpenAvenue and they've been busy enough just trying to figure out what
> they've got and what to do with it. Now that they've got a couple of
> dedicated people on board and they're getting up to speed, I'm hoping
> that we can do a release in the not-too-distant future. I'd suggest
> doing an official release (CVS 1.11) instead of another interim release;
> the current official release is two years old and has lots of known
> bugs, whereas the current development version is quite stable.
I agree. CVS 1.10 has Y2K bugs and we are already in the post-Y2K world.
There are many bug reports about CVS 1.10, and they are mostly useless
now.
People (especially sysadmins) should be encouraged to use the current
version.
I hope that the security issues will be addressed promptly. However, the
documentation should recommend using chroot to limit yet to be discovered
vulnerabilities, especially when public read-only access is used. In this
case using CVS 1.11 will not require immediate upgrade to 1.11.1 to plug
the next security hole.
However, I believe that the 1.11 should be the branch point. The stable
branch would be used for high-priority fixes only. Developers on the head
branch should feel free to make radical changes.
Regards,
Pavel Roskin
