[zfs-devel] github bug maintenance shortcomings

Darik Horn dajhorn at vanadac.com
Sat Jul 18 10:31:15 EDT 2015


On Sat, Jul 18, 2015 at 6:34 AM, Zenaan Harkness via zfs-devel
<zfs-devel at list.zfsonlinux.org> wrote:
>
> I hope this is on topic, my apologies if I've posted to the wrong
> list. I've subscribed for now, so you don't need to CC me separately.

Pinging bugs is okay.  Don't feel ignored; people fade-in and fade-out
of participation cyclically.

That said, framing the ZoL workflow against other projects is oblique
to actually fixing the bug.  Debian's workflow satisfies its social
and political goals in a way that often reduces productivity in other
organizations.

The sector retry quirk is inherited from Solaris and happens by
design.  Demonstrating a larger risk surface beyond that already
described in the bug report could motivate somebody to work on it.

Furthermore, the ticket got a scheduling milestone, so unless the
proposal for distributed-maintenance means that maintenance can be
distributed to a new trusted contributor, then there isn't much else
to do.

Ticket #1256 is a good place to dig in.  The bug report is accurate
and informative, the undesirable behavior happens for understandable
reasons, and there are at least two potential ways to get resolution.


More information about the zfs-devel mailing list