mcuee
mcuee
As of now, for the PRs listed for 1.0.30 release, we still have one PR open. * https://github.com/libusb/libusb/milestone/14 * #1512 @sonatique and @tormodvolden Please look at the above PR to...
Looks like #1512 will be merged soon. @tormodvolden @sonatique and @seanm I am wondering if we should target the 1.0.30 release in about two months time, say by the end...
Usually we will have one or two RCs before release. No need to freeze so early. https://github.com/libusb/libusb/releases Recent releases by @tormodvolden. 1.025-rc1 -->Jan 22, 2022 1.025 release --> Feb 1,...
@sonatique @tormodvolden and @seanm Specific to Windows related PR, I think the following PRs are ready for review. Please take a look. Some of them have been there for quite...
@sonatique @tormodvolden and @seanm The other long standing PR is for Android. Not so sure if we can do anything about it. * https://github.com/libusb/libusb/pull/1164 It was the conrinuation of PR...
BTW, I am trying to clean the old issues and I may choose to close some issues. I would also like to close some old PRs but I will ask...
New macOS 26 related issue: * #1661, fixed by PR #1700 * #1701, need more details,
From @sonatique https://github.com/libusb/libusb/issues/1661#issuecomment-3306038303 > I merged PR [#1700](https://github.com/libusb/libusb/pull/1700) . [@mcuee](https://github.com/mcuee) can we close this issue as well? > > [@mcuee](https://github.com/mcuee) [@tormodvolden](https://github.com/tormodvolden) : I am not yet familiar with libusb release...
My opinion https://github.com/libusb/libusb/issues/1661#issuecomment-3306225544 > [@sonatique](https://github.com/sonatique) > > I will prefer we release from the git master branch. > > We have never done otherwise. > > Usually we will one...
@sonatique, @tormodvolden and @seanm My suggestion is that we still release based on git, if we encounter issues for libusb-1.0.30 release, we can always release 1.0.31 as a bug fixe...