Bug#930801: unblock: rdma-core/22.3-1

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#930801: unblock: rdma-core/22.3-1

Benjamin Drung-6
Package: release.debian.org
Severity: normal
User: [hidden email]
Usertags: unblock

Hi,

rdma-core is maintained by the Linux RDMA group. It follows the Linux
kernel release schedule and concepts. Upstream backports fixes to their
stable branches. We have currently rdma-core 22.1-1 in Debian
unstable/testing. Upstream released 22.3 which contains only bug fixes.

I prepared an updated package 22.3-1 (patch attached). Before uploading
anything, I like to hear your opinion: Is this change okay for buster,
should I wait for the release, or better keep that update out of buster?

unblock rdma-core/22.3-1

--
Benjamin Drung
System Developer
Debian & Ubuntu Developer

1&1 IONOS Cloud GmbH | Greifswalder Str. 207 | 10405 Berlin | Germany
E-mail: [hidden email] | Web: www.ionos.de

Head Office: Berlin, Germany
District Court Berlin Charlottenburg, Registration number: HRB 125506 B
Executive Management: Christoph Steffens, Matthias Steinberg, Achim
Weiss

Member of United Internet

rdma-core_22.3-1.debdiff (23K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Bug#930801: unblock: rdma-core/22.3-1

Paul Gevers-4
Control: tags -1 moreinfo

Hi Benjamin,

On 20-06-2019 23:31, Benjamin Drung wrote:
> rdma-core is maintained by the Linux RDMA group. It follows the Linux
> kernel release schedule and concepts. Upstream backports fixes to their
> stable branches. We have currently rdma-core 22.1-1 in Debian
> unstable/testing. Upstream released 22.3 which contains only bug fixes.

I am going to quote my response to bug 930293.

"""
During the freeze we only want targeted fixes for bugs of severity
important and higher (BTS definition) [freeze-policy], yes [...] but
it's possible that new upstream releases *are* targeted bug fixes.
However, [...] you as the maintainer have to do the checking. [...]

We have had multiple unblock requests
where the maintainer was evaluating the changes done upstream and
convinced themselves that they all qualified. By doing the evaluation
they were often able to convince us. In some cases they didn't. I can
only assume that a lot of unblock requests were not filed because the
maintainer couldn't convince themselves.

[...]

Upstream releases are not acceptable at this moment in the release.
After what I wrote above, obviously with the exception where you can
convince yourself and us that *everything* in the release is qualifying
our freeze criteria [freeze-policy].
"""

> I prepared an updated package 22.3-1 (patch attached). Before uploading
> anything, I like to hear your opinion: Is this change okay for buster,
> should I wait for the release, or better keep that update out of buster?
>
> unblock rdma-core/22.3-1

Without more information from you, I believe it is too late for buster.

Paul


signature.asc (499 bytes) Download Attachment