I would vote to release an RC rather than a full blown release on account that:
1. People who want a release should be able to use the RC just as well (plus
if it can get our users into the habit of actually testing RCs rather than wait
for the release, so that we identify these kind of bugs before then, that
wouldn't be a bad thing)
2. We're picking a few two many issues here, and I'd rather see the next
release address them all and avoid creating new ones.
3. I'd be more comfortable if Hans had a chance to look at the proposals, and
going RC until Hans is back seems like an effective way to achieve that.
4. Since I'm planning to keep my involvement with libusbx at a minimal level
over the coming weeks (Rufus) I wouldn't mind having Nathan handling the
libusbx release process... but with the safety net that an RC provides.
Does that sound OK? Or do we think that an RC won't be enough to compensate for
a bugfix release ASAP?
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/121#issuecomment-21374250
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
