On Sat, Mar 16, 2013 at 9:23 AM, Pete Batard <p...@akeo.ie> wrote: > On 2013.03.15 00:55, Xiaofan Chen wrote: >> So 2.0 will be kind of experimental or "subject to change". > > And that is why we have an easy way to let developers identify API > compatibility issues, through LIBUSBX_API_VERSION in libusb.h. This > wasn't an entirely innocuous addon you know... > >> No issue for the 1.x branch. But rather issues for 2.0 users >> since it may subject to be changed. > > See above. Libraries are no special case. Software has to to evolve. But > again, we're not going to force anyone to evolve at the same pace we do.
Okay I think I understand your points of view and I am fine with it. So we will stick to a 2.0 release and then 2.1 release on hotplug. >> One possibility is to go to the 2.0 branch and work on hotplug >> but without the release of 2.0, i.e., merge 2.0/2.1. How do you >> like the idea? > > Do you really believe I can subscribe to the idea of keeping releases > under wraps, when lack of releases and utter disregard for RERO from > libusb is the reason I joined the libusbx fork? Okay. >> During the discussions of hotplug, there may be more places to >> optimize the API and introduce new API changes >> if necessary. > > Yep. Which can be done with 2.1, 2.2, 3.0... Luckily for us, it's not > like integer numbers are finite... ;) Good. > This being said, I feel like, once more, I need to kill in the bud the > recurring idea that, somehow, I'm going to push for a new major libusbx > release every other 3 months or so. I can't shake the feeling that some > people around here are irrationally worried about that. > Even if I really wanted to, which I don't, I'd never have enough spare > time to go into that fast a release cycle. I am fine with fast release cycle when there are many missing features and there are constant patches and feature requests coming in. But I am also realistic that it is not possible for a small project to have a 3-month release cycle for major feature release. Once a library becomes quite stable, then the release will become much slower, an example is libusb-win32. -- Xiaofan ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
