Re: Unstable files/documentation & package formats

> Why not simply making a CVS branch. This exactly what it does...

Of course you can do that with CVS, but in my opinion it is something of a hassle
when you are just doing quick and dirty stuff. In the case of the documentation,
I might have just one file changed that I want to put up where everyone one can 
get at it. Perhaps I will get numerous feedback about typos and such which can
be updated quickly, but serve little purpose in CVS for revision control.

The sourceforge project file web interface just seems a little more accessible for 
this purpose.

I am not trying to complicate issues by my suggestion and perhaps this is not the 
way things have traditionally been done. Maybe a little change in packaging/file 
management/availability will open things up to more participation. If not, no real
harm done (CVS and tar.gz remain in place throughout). And of course I am quite
willing to help out. Since I am making these suggestions I am ready to make
packages and manage the files I'll upload in accord with requirements, as well as
keep the devel/user lists notified of any changes.


Raymond
__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf