Previous discussions suggested that we do a release on 1 March (St
David's Day).  If we are to stick to that we need to freeze code on
Tuesday to allow for packages to be built.

Based on last release, is this correct
      NAME                                      RESPONSIBLE
 	csound_5.05.0-1_i386.deb                jpff
  	csound-5.05.0-1.i586.rpm                ??
  	Csound5.05-i386d.tar.gz                 jpff
  	Csound5.05-i386f.tar.gz                 jpff
  	Csound5.05_manual_A4_pdf.zip            Andres
  	Csound5.05_manual_htmlhelp.zip          Andres
  	Csound5.05_manual_html_single.zip       Andres
  	Csound5.05_manual_html.zip              Andres
  	Csound5.05_manual_pdf.zip               Andres
  	Csound5.05_OS9.smi.bin                  Anthony
  	Csound5.05_OS9_src.smi.bin              Anthony
  	Csound5.05_OSX10.3.tar.gz               Victor
  	Csound5.05_OSX10.4.tar.gz               Victor
  	Csound5.05-src.tar.gz                   jpff
  	Csound5.05-src.zip                      jpff
  	Csound5.05-win32-d.exe                  Michael
  	Csound5.05-win32-f.exe                  Michael
  	Csound5.05-x86_64d.tar.gz               jpff
  	Csound5.05-x86_64f.tar.gz               jpff
  	Loris_STK_src_5.05.zip                  ??
  	tutorial_5.05.pdf                       jpff

While about it, what are the outstanding bugs?
I hear about ambidecode and read/write OSC; any others?

==John ffitch

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net