[Libusbx-devel] Keeping the 1.0.9rc3 tag

[Xiaofan Chen]

On Sun, Mar 25, 2012 at 12:53 PM, Xiaofan Chen <xiaofanc at gmail.com> wrote:
>> When I have a chance, I'd also like to set a wiki page with the current
>> plan for releases, and what we think should go in each of them, so that
>> we all can be on the same page and get an estimate of the task ahead.
>
> Yes that is good to have.
>

Some of my rough ideas.

I think we can have two branch of development.
1) libusbx 1.0.x branch (API compatible with libusb-1.0)

For this branch, major work will be to bring Windows backend
up to the functionality of the other OS (e.g.: isoc support).

1.0.9: first fork release (xusb, bug fix etc), infrastructure setup

1.0.10: first "feel-good" release, I am not so sure what should
be in here. You mentioned versioning and I have a proposal.
Let's see how people like the proposal.

1.0.11: re-add features like HID

1.0.12: libusb0.sys/libusbk.sys integration, the approach may need
to be discussed. Currently my idea is to use Graeme's approach
without depending on libusbk.dll: directly talk to the kernel driver.
But this may need quite some work.

2) libusbx-development branch:
Initially API compatible with libusb-1.0 with major added
API like hot plug, later can be API incompatible.

The focus for the core should be the next 1.1
(or call it 2.0 or 3.0) release, example can be
like Hotplug and async API improvement. All OS
will need quite some work.


-- 
Xiaofan