Perhaps leaving the cvs zip/tar with a simple text file enclosed explaining that the cvs is obsolete and where the new svn code resides, as well as a link to the svn program might be better?
This would solve 2 problems: 1. Those who don't read the FAQ or readme first (shame on you!), this would solve all the unessary questions, like where do I get svn, where is the trunk located, etc. 2. Those who use some sort of automated download via crontab or what not to grab latest code (those that don't actually view the website), this would inform them of where to get the latest code and allow them to adjust their scripts accordingly. -- Regards, Jon Malte S. Stretz said: > Hiho, > > seems like some people didn't notice that we moved to the ASF SVN and > still > report bugs against the latest SF.net CVS. > > To make clear that that code is obsolete, I suggest that we remove all > code > within the "spamassassin" and "pop3" module to the Attic and just leave a > README which tells the user what has happened. That file would also > contain > a description on how to get the latest version of the SF.net CVS code if > somebody still needs it for some reason (a simple 'cvs up -D 2004-01-01' > should do the trick). > > What do you think? > > Malte > > -- > [SGT] Simon G. Tatham: "How to Report Bugs Effectively" > <http://www.chiark.greenend.org.uk/~sgtatham/bugs.html> > [ESR] Eric S. Raymond: "How To Ask Questions The Smart Way" > <http://www.catb.org/~esr/faqs/smart-questions.html> >
