Hey folks,

Despite the firmware upgrade code not working on all remotes yet, I'd like
to start prep'ing for the 0.20 release and aim to get it out early next
week. The rename and library split are stable at this point, and the
majority of the API is stable.

Here's what I see as needing to be done before release:

 - rename libconcord/concordance.h to something else (see previous email)
 - I'd like to get the setupapi.h thing worked out of possible
 - final test on Windows of current code
 - ask SF to remove the whole examples/ directory (I'll do that today)

Anyone else have anything they think needs to be in 0.20?
-- 
Phil Dibowitz                             [EMAIL PROTECTED]
Open Source software and tech docs        Insanity Palace of Metallica
http://www.phildev.net/                   http://www.ipom.com/

"Never write it in C if you can do it in 'awk';
 Never do it in 'awk' if 'sed' can handle it;
 Never use 'sed' when 'tr' can do the job;
 Never invoke 'tr' when 'cat' is sufficient;
 Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming


Attachment: signature.asc
Description: OpenPGP digital signature

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
concordance-devel mailing list
concordance-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/concordance-devel

Reply via email to