CVS maintenance question
Hello CVS package maintainers,
My name is Assaf, I'm a volunteer sysadmin at gnu savannah (the gnu code hosting platform), and I'm writing to you because you are listed as the CVS package maintainers for your respective distributions.
I apologize for cross-posting, and ask you to be mindful before "replying to all".
I invite you to continue this discussion on the "cvs-dev@nongnu.org" mailing list.
We are in the process of upgrading savannah's infrastructure, including our CVS daemons.
We noticed that the last stable release was 1.11.23, and the latest unstable/feature release was 1.12.13 - both many years old.
Each distribution uses a different version, but all maintain a hefty amount of patches on top of that version.
For savannah we need some features that were committed after 1.12.13, so we can't even use the packaged version.
And so we are trying to find the optimal route to continue with CVS.
First,
If any one of you is interested in stepping up to be the chief upstream maintainer of cvs - that would be welcomed.
Some current CVS maintainers expressed willingness to help to any new maintainer.
Perhaps this could usher a new long-due release.
Second,
If you have any recommendation as to the best way to proceed, any critical patches you think should be applied -
all these and any other comments are welcomed.
For example, why did Centos/Redhat/Fedora choose 1.11.23, while Gentoo - 1.12.12, and Debian/Ubuntu used 1.12.13 ?
Many thanks in advance,
- assaf
Reply to: