For 2.0 release, I think we label it as "API change only" release unless critical bug fixes are required. Let's keep it that way. I will not add any other issues to the 2.0 milestone unless there are other API changes required. https://github.com/libusbx/libusbx/issues?milestone=9&state=open
After 2.0 release, I think we need to discuss how to proceed again. For 2.1, hotplug is certainly the main thing. So most of the issues are related to that. #84 and #46 are nice to have but not essential so we can remove them if https://github.com/libusbx/libusbx/issues?milestone=7&state=open The timing of 2.0/2.1 are just preliminary and can be changed as well. 2.2 and 2.3 are just too far away to be discussed for now. :-) Then I also created the other two milestones since Hans mentioned the desire to continue the 1.0.x series without the API change in V2.0. Apparently it is not possible that 1.0.16 uses the simple hotplug API and 1.0.17 uses the 2.1 hotplug API. So that needs to be changed. So I think we need to decide whether 1.0.16 is a go or need to be deleted. https://github.com/libusbx/libusbx/issues/milestones?with_issues=no -- Xiaofan ------------------------------------------------------------------------------ Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
