You can have a look at
<URL:http://www.loria.fr/~molli/cvs/cvs-tut/cvs_tutorial_toc.html> to
find out more.
> I wouldn't mind injecting my work on the Coolscan Backend into CVS.
> It needs some changes to sane.h and I was wondering what I have to
> do to get them accepted and included.
Well, the CVS server will not solve that problem. All API changes
must still be agreed upon before changes are made. The only thing CVS
does it making the change available when it is done.
[Nick Lamb]
> Does someone have the TIME to do the thankless donkey-work required
> for Release Early and Often on a big project like SANE?
I beleave a CVS repository with write access to all maintainers would
make it easy to release often. Anyone can do 'make dist' at any time
to generate a distribution and upload it to the ftp site.
Some projects have 'release-masters' to do this job. Once in a while,
one must have code freeze to make a proper release, but most bugs
should already be fixed because of the tested snapshot releases.
David should not have to do all the work. When he has little time to
spare, it creates a bottle-neck in the development process.
-- ##> Petter Reinholdtsen <## | pere@td.org.uit.no O- <SCRIPT Language="Javascript">window.close()</SCRIPT> http://www.hungry.com/~pere/ | Go Mozilla, go! Go!
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com