sts-sponsors team mailing list archive

[Dan Streetman <1771740@xxxxxxxxxxxxxxxxxx>]

@nicolasbock before sponsoring, can you cover a few of the steps in the
SRU process:

1) The SRU template in the description isn't actually filled in, I think
you simply copy-n-pasted the actual template text in...it does need to
be actually filled out

2) This is marked as affecting f/h/i, but you only included a debdiff
for focal; are h and i already patched or not?

3) You mentioned in chat that the netplan maintainer suggested you just
SRU the changes as the next scheduled release for netplan is not for a
while; I assume it was @slyon you talked to? I added him in this bug as
a fyi; @slyon if you have any concerns about SRUing this before the next
regular netplan release please let us know.

Thanks!

** Tags added: sts-sponsor-ddstreet

-- 
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1771740

Title:
  Expose link offload options

Status in netplan:
  Fix Committed
Status in netplan.io package in Ubuntu:
  New
Status in netplan.io source package in Focal:
  New
Status in netplan.io source package in Hirsute:
  New
Status in netplan.io source package in Impish:
  New

Bug description:
  [Impact]

   * An explanation of the effects of the bug on users and

   * justification for backporting the fix to the stable release.

   * In addition, it is helpful, but not required, to include an
     explanation of how the upload fixes this bug.

  [Test Plan]

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
     package to reproduce the bug and verify that the updated package fixes
     the problem.

   * if other testing is appropriate to perform before landing this update,
     this should also be described here.

  [Where problems could occur]

   * Think about what the upload changes in the software. Imagine the change is
     wrong or breaks something else: how would this show up?

   * It is assumed that any SRU candidate patch is well-tested before
     upload and has a low overall risk of regression, but it's important
     to make the effort to think about what ''could'' happen in the
     event of a regression.

   * This must '''never''' be "None" or "Low", or entirely an argument as to why
     your upload is low risk.

   * This both shows the SRU team that the risks have been considered,
     and provides guidance to testers in regression-testing the SRU.

  [Other Info]
   
   * Anything else you think is useful to include
   * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
   * and address these questions in advance

  [Original Description]

  https://www.freedesktop.org/software/systemd/man/systemd.link.html has
  a number of [Link] options which I need to use for a flaky network
  card (TCPSegmentationOffload, TCP6SegmentationOffload,
  GenericSegmentationOffload, GenericReceiveOffload,
  LargeReceiveOffload) which are not exposed via netplan.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1771740/+subscriptions