Lionel Debroux wrote: > The maintainer of libusb has proved, for two years, to be a roadblock on > the path of advancing the state of libusb and on making life easier for > users.
I think it would be fair of you to look closely at the repository history before we discuss if and how I advanced the state of libusb. There are a few hundred commits to look into, and I encourage you to compare them with their corresponding proposed patches. Unfortunately that's the only way to accurately measure my activity that I can suggest. I would be happy to visualize it for you if I knew of a good way, but I haven't come up with one. If anyone has suggestions, please share. The long release cycle is a dead horse; bystanders and users wrote emails asking for a release, but unfortunately noone took initiative to create a release branch. I only heard the idea to do a 1.0.8.1 release with some subset of commits taken from master after 1.0.9 was already out. The idea is really good and I wish someone had suggested it sooner - it would have been very easy for anyone who wanted to get involved, and even easier for me, to do some cherry-picking to make such a release branch. Alas I had tunnel vision on the master branch, noone helped me out of that, and 1.0.9 took too long. I think it turned out very good once it was done, but anyway, everyone is busy working on new and even better versions now. :) //Peter ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
