libusbx v1.0.9 has been released

[Pete Batard]

Available from the files repo at [1] as well as git of course.

As long as our wiki and API documentation remains skeletal, and we 
haven't sorted versioning, I'd refrain from announcing anything publicly 
and wait a couple of weeks for 1.0.10, though I'm not going to prevent 
anybody from doing so if they feel like it.

Next up, I'll see if I can spend spend some time on the wiki and stuff, 
but I'm fairly, huh let's say "annoyed", at having to duplicate what I 
already did on Segher's old host, since its wiki has now gone out...

If you look at the wiki, you'll see that its only original content right 
now is a page for maintainers with a release-checklist [2]. I hope I 
haven't missed anything there, but if you feel I have, either edit or 
let me know. You'll see that one of the points listed aims at ensuring 
that trac is up to speed with the latest version and that any new 
incident will default to that one. I also created components in trac so 
that if you log an issue, you'll be able to select whether it is against 
a specific backend or core/common. Not sure if we want to break it down 
further (such as sync API, async API, etc.) as new issues would 
typically be logged by people who aren't entirely unfamiliar with libusbx...

Unfortunately, it doesn't look like we can configure trac to copy the 
mailing list on incident updates, as SF's trac support is a bit subpar, 
so we'll have to monitor new issues manually which sucks. Trac git 
integration is also something that SF didn't bother providing. On the 
admin page, they seem to provide the required trac modules but if you 
try to activate them, you 'll find out that you can't. I've seen a 
regular posts where SF have been promising they'll work on it, but 
nothing so far...

Current ETA for libusbx-next (v1.0.10): 2012.04.16.

Regards,

/Pete

[1] https://sourceforge.net/projects/libusbx/files/
[2] 
https://sourceforge.net/apps/mediawiki/libusbx/index.php?title=Maintainer