To view parent comment, click here.
To read all comments associated with this story, please click here.
Not always, but when I do, I take my time to investigate alternatives that might bring me more for my time and money.
It just seem pointless to me to reinvent the same old wheel, especially when there are ways to build newer and better wheels nowadays. That said, the OpenBSD team is completely free to do whatever they want: it's their project and it's not like it's gonna change my life.
They obviously disagree with you that CVS is fundamentally obsolete. Sure Linus didn't like CVS, but all that means is that Linus didn't like CVS, not that CVS is obsolete. And given that they have far more experience with large scale collaborative software development than I have, I'm certainly not going to argue with them.
Well, it's not like CVS is going to bit-rot projects that are still using it. However, many high-profile open-source projects and enterprises are moving to alternatives because they are improving the collaborative experience for their users. After using SCMs like SVN, Hg or Perforce, it's a bit hard to get back to CVS.
I just wonder why the OpenBSD folks didn't started up a brand new project instead of working around CVS.




Member since:
2005-06-30
To what I understand, OpenCVS is a reimplentation of CVS with better security and access control while staying compatible with the original as much as possible. At least, it's how they are advertising it. They cannot add or remove many features if they want it that way. Even if they change their minds, they are still building a new solution based on something that is obsolete.
I believe it would just be more productive to start up a new SCM.