Moreover, I would prefer to not have Debian users showing up here, asking for support for an "outdated" version, taxing upstream developer's time. Conversely, the 0.8-branch might simply receive no more attention at all-and there are already many changes relative to that branch that prevent git cherry-pick from applying cleanly. The 0.8-branch picked up some significant features throughout its lifetime, so there's a concern that an early 2.0 or perhaps 2.0.1 might be left in the past, with bug fixes that may need significant back-porting to apply to such an old release (and I'm thinking far down the line, say at least 3 years). It's (perhaps oddly) not Debian policy to import new point releases, but rather cherry-pick these targeted fixes. What are the plans to provide noninvasive, targeted bug fixes for each of these branches?įrom the perspective of downstream Debian, we'd like to only be including the least dangerous possible fixes-this means avoiding things like any new features and even future kernel compatibility (since we aren't upgrading the kernel either).In my opinion, there is really one point that is of primary concern for Debian stable. Downstream in Debian, we're trying to decide if Debian 11 should ship with the ZFS 2.0-branch or the 0.8-branch.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |