Preparing for Kinetic Sync 2020-09-24

Packaging and Release Management Kinetic
1

Kinetic Maintainers,

We have 34 packages ready to sync and no regressions. As such I plan to hold new releases into Kinetic and make a sync on Monday 2020-09-28T07:00:00Z

If there’s any issues that should be triaged before this sync, please reply here.

2

Not a regression nor an obvious bug, but there’s a design argument in a new msg package computer_status_msgs#2. Although I don’t expect there’s a user for that pkg yet (esp. for Kinetic since the binary hasn’t been out yet), if we decide to remove some messages after the 1st release that can cause downstream breakage in theory. I’m happy to take whatever action to minimize such an impact, but I need an input. @tfoote since you started that ticket, would you mind giving a guidance there?

3

As a new leaf packages you should have little to no disruption. It would be good to make sure that your documentation indicates the level of stability that you intend to maintain over what periods.

The sync is out

1 Like