ETAs for libusbx operability and first release?

[Xiaofan Chen]

On Mon, Feb 13, 2012 at 4:25 PM, Segher Boessenkool
<segher at kernel.crashing.org> wrote:
>>>> That's not going to happen.  If we pick up stuff that still needs
>>>> testing, we cannot release.
>>
>> I would not call most of those "needs testing".
>
> The branch is called "testing", and the branch rebases at least
> some of the time.  I'm not going to merge from that, it will
> become a mess.  If you want me to merge patches for our 1.0.9,
> please send them now, to this mailing list.
>

I agree with your decision not to merge the libusb.git
testing branch since you are right it is called "testing"
and the branch often keeps rebasing itself.

On the other hand, I think now Peter has commited
the patches to mainline libusb.git as well. So I think
it is good that libusbx git can catch up with libusb.git
master branch now that it has some must-have and
some nice-to-have patches for the 1.0.9 release.

If Peter can release the current libusb.git as 1.0.9,
that would be best. But no one can predict what
Peter will do -- occasional burst mode activities
and then goes into sleep mode -- quite good in
terms of energy consumption on his part, but not
that good for the project. :-)

So I think it is good to catch up with libusb.git. And
then if Peter does not come out with a release within
one or two weeks, it is good to release 1.0.9
libusbx fork.


-- 
Xiaofan