Guidelines - Server merges for Judicious Jacana

[Bryce Harrington]

Here are some guidelines on how to use the bug reports to aid us in
tracking this work consistently:

  * Syncable packages: If a package merge should actually be a sync from
    Debian rather than a merge, change the tag from 'needs-merge' to
    'needs-sync'.

  * Multi-merges: If a package is going to need more than one merge in a
    cycle, just file additional bug report(s) as needed.  Make sure they
    are filed against the package in question, tagged 'needs-merge', and
    either have a milestone set or 'Scheduled-For'.

  * Package-sets: If you have several packages that need to be processed
    together at the same time and prefer a single bug report for
    tracking all that, feel free to close all the bug reports except
    one, and just add the other packages as bug tasks.

  * Later: Merges that are postponed to next cycle can be targeted to
    the 'later' milestone.

  * Backlog: Packages that are not priorities to be merged can be set to
    importance 'WISHLIST'.

Don't forget to include the LP# of these merge bug reports in your
changelogs or syncpackage runs.

Bryce

P.S., Also, note that there are additional bug reports to come for
merges from upstream, backports, ppa updates, and so forth.


On Wed, Oct 13, 2021 at 09:27:36AM -0700, Bryce Harrington wrote:
> Hi all,
> 
> Each release we aim to ensure each package the server team cares for
> gets at least one merge from Debian.  To coordinate this work
> efficiently amongst us, we forecast which packages are likely to have
> merge opportunities during the cycle and then self-assign items.
> 
> In the past we've used a Trello board to schedule these tasks, but as
> that is retired this cycle, we'll instead be using bug reports in
> Launchpad.
> 
> For Jammy there are 80 server packages that look like they might need a
> merge during the cycle:
> 
>    https://bugs.launchpad.net/~canonical-server/+subscribedbugs?search=Search&field.tag=needs-merge
> 
> Please review this list today and set yourself as the assignee for
> merges you wish to work on this cycle.
> 
> Tomorrow we'll look over what remains and divide assignments between us.
> 
> Bryce