Unless we find something critical, I STRONGLY vote to delay it until after
1.0.18, even if it's doc.
As Murphy's day (yesterday) taught me, if there's anything that can go
wrong when duplicating work, it will go wrong. The github sudden breakage
[1], which you are aware of, and which thankfully happened before we went
live, was only the tip of the iceberg (for instance, the machine I used to
upload the doc from has no working doxygen right now...).
If something's gotta break, I'd rather have it break when there's only a
single release being pushed out... ;)
Of course, anything that looks critical is go (and right now I'm wondering
if the infinite loop fix that was just submitted qualifies)...
Regards,
/Pete
[1] https://status.github.com/messages
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
