[prev in list] [next in list] [prev in thread] [next in thread] 

List:       libusb-devel
Subject:    Re: [libusb] Libusb maintainership / "hiring" a release manager
From:       Pavel Grunt <pgrunt () redhat ! com>
Date:       2016-08-15 8:57:24
Message-ID: 1471251444.1827.10.camel () redhat ! com
[Download RAW message or body]

Hi,

On Wed, 2016-08-10 at 14:29 +0200, Hans de Goede wrote:
> Hi,
> 
> On 26-07-16 11:14, Hans de Goede wrote:
> > 
> > Hi,
> > 
> > On 19-07-16 18:58, Nathan Hjelm wrote:
> > > 
> > > Since no one has stepped up I am willing to roll the release tarballs for
> > > the next release. Can't help with Windows though.
> > 
> > First of all thank you!
> > 
> > About the current rc-s they seem to lack the race fixes Chris Dickens
> > has done and I've built upon, these have been posted to the list, but
> > they can also be found here (easier):
> > 
> > https://github.com/jwrdegoede/libusbx/commits/master
> > 
> > Note before applying these "bd8d5b5019b72b2dc2d074d96c9992e2f6e7e0b7"
> > should be reverted, this series fixes the same bug in a different
> > way.
> > 
> > It would be great if these can make it into a 1.0.21-rc3.
> 
> Ping ?
> 
> I've rebased my master branch on top of 1.0.21-rc2 (reverting
> "bd8d5b5019b72b2dc2d074d96c9992e2f6e7e0b7" as the locking fix
> series which has been pending for quite a long time now
> conflicts with it and fixes the same issue).
> 
> I would like to see us move forward with both getting 1.0.21
> released and with getting the locking improvements Chris Dickens
> and me have been working on merged. Since my work is basically
> a review + cleanup of Chris' work and no-one else seems to
> have time to review it I suggest merging it as is (if it was
> not for the 1.0.21 release pending I would just push it).
> 
> So I see 2 ways forwards:
> 
> 1) Merge my master branch, release as 1.0.21-rc3, wait a bit,
> then do 1.0.21 release
> 
> 2) Do a 1.0.21 release based on rc2, merge the locking fix /
> rework series afterwards.
> 
> I've a slight preference for 1. but both are ok. Note I've just
> updated the Fedora 25 and later libusb packages to 1.0.21-rc2 +
> the locking series (so in essence to what I suggest becomes
> 1.0.21-rc3. I'll keep an eye out for any bug reports caused
> by this.

Just a comment from spice-gtk space: I tested "1.0.21-rc2 + the locking series"
on Windows with spice-gtk and it was working fine. Without the locking series
spice-gtk was freezing.

Pavel
> 
> Regards,
> 
> Hans
> 
> 
> 
> > 
> > > 
> > > -Nathan
> > > 
> > > > 
> > > > On Jul 12, 2016, at 2:44 AM, Hans de Goede <hdegoede@redhat.com> wrote:
> > > > 
> > > > Hi All,
> > > > 
> > > > libusb development seems to have stalled lately. Specifically we
> > > > seem to be doing a bad job wrt getting the next release out the
> > > > door.
> > > > 
> > > > Personally I have moved mostly on to other projects and would very
> > > > much like someone else to take over maintaining the linux libusb
> > > > bits.
> > > > 
> > > > Besides that we also really need someone to fulfill the release-manager
> > > > role, tag and release -rc's and then a final release, etc.
> > > > 
> > > > So any volunteers for either role ? Anyone know anyone who might
> > > > be a good candidate who we could ask ?
> > > > 
> > > > Regards,
> > > > 
> > > > Hans
> > > > 
> > > > ------------------------------------------------------------------------
> > > > ------
> > > > What NetFlow Analyzer can do for you? Monitors network bandwidth and
> > > > traffic
> > > > patterns at an interface-level. Reveals which users, apps, and protocols
> > > > are
> > > > consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> > > > J-Flow, sFlow and other flows. Make informed decisions using capacity
> > > > planning
> > > > reports.http://sdm.link/zohodev2dev
> > > > _______________________________________________
> > > > libusb-devel mailing list
> > > > libusb-devel@lists.sourceforge.net
> > > > https://lists.sourceforge.net/lists/listinfo/libusb-devel
> 
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are 
> consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
> J-Flow, sFlow and other flows. Make informed decisions using capacity 
> planning reports. http://sdm.link/zohodev2dev
> _______________________________________________
> libusb-devel mailing list
> libusb-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/libusb-devel

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. http://sdm.link/zohodev2dev
_______________________________________________
libusb-devel mailing list
libusb-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusb-devel

[prev in list] [next in list] [prev in thread] [next in thread]