2013/6/10 Pete Batard <p...@akeo.ie>: > On 2013.06.10 17:42, Nathan Hjelm wrote: >> Peter's time has gotten to be very limited so I have opted to take over >> maintenance of >> libusb. I have been in contact with the libusbx team to and invited them >> to rejoin libusb >> as maintainers and they have accepted. The plan is for us to work >> together in a 1.0.16 >> release of libusbx. This release will be the combination of the libusbx >> codebase and my >> efforts on libusb 1.0.16 and will be the final release of libusbx. After >> 1.0.16 is >> out we plan to rename the libusbx github group to libusb and wind down >> the libusbx >> sourceforge project. From that point on the official libusb repository >> will be at github >> (this includes libusb-compat-0.1). >> >> More details will be available (some things may change) as we get closer >> to finally >> merging the two projects. > > I'll just add to this that, as you've seen from recent work on libusbx, > and with everybody's help, the effort to merge the content of the two > codebases is already well underway. I'll also point out that Nathan was > added as a maintainer of libusbx some time ago. > > While we hope to make the transition back into a single libusb > distribution as smooth as possible, there are some changes that will be > unavoidable for libusbx users, such as switching the git repo as well as > the mailing list. Of course, we will provide you with ample notice > before it happens. > > Also, as pointed out by Nathan, the upcoming re-merged libusb is planned > as a direct continuation of libusbx, so the effort to transition back to > libusb, for libusbx based apps, is expected to be minimal. > > For instance, if you follow libusbx through git, you should just have to > change your repository base (which is also something libusb followers > will have to do), or, if you use tarballs, you will just need to pick it > from a different location, which we will also point you to. > > Overall, we think that the decision to merge libusb and libusbx back > together, when the main obstacle that prevented regular libusb releases > can be circumvented, is something that both libusb and libusbx users can > benefit from. Therefore we hope that everybody will welcome this change. >
Would be possible to rejoin the mailing lists earlier? Sometimes I don't know which mailing list I am supposed to send messages to (libusb, libusbx or both?). -- Best Regards, Wander Lairson Costa ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
