On 2013.06.11 11:10, Hans de Goede wrote: > I think it would be good to tag current master as 1.0.16-rc1, spin > tarbals, etc.
I'd prefer if we don't tag the RC-1 until next Monday, on account that: - I'd like to keep at least a little distance between 2 major events, such as the announcement of libusbx and libusb merging back and libusbx getting into release mode. There's the possibility that, since libusbx is planned to be the effective continuation of libusb, people over at libusb may request a few things from the next libusbx release. - It's nice to give people a few days before RC gets into effect, in case they are working on something they'd like to see integrated, before we freeze the addon of new features. - It'll give us exactly 2 weeks of RC time to the officially planned release, as per our milestones, which I think is what we agreed on for RCs. > I'm willing to the work for this (*), with the exception of providing > windows binaries. Sounds good to me. Thanks. > Pete, I believe that you've a checklist for the release process somewhere ? Hidden in plain sight, at https://github.com/libusbx/libusbx/wiki/Maintainers%27-Corner#wiki-RCRelease_work > Also I guess we should update the README with some blurb about libusbx > merging back into libusb ? Yup. But I guess we have till the planned release to come up with something. Anybody wants to volunteer to propose something? Regards, /Pete ------------------------------------------------------------------------------ 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
