On Thu, Jul 20, 2023 at 05:23:24PM -0300, Lucas Kanashiro wrote:
> > > I've made some changes to
> > > those packages and now we would need the following:
> > >
> > > - docker.io and containerd: check for merges against Debian
> > > - docker.io-app, containerd-app and runc: check for merges against
> > upstream
> > >
> > > And for the backport for stable releases (not exactly a MRE but that's
> > the
> > > nomenclature we have been using here), I'd like to track just
> > > docker.io-app, containerd-app and runc.
> >
> > Gotcha, so sounds like for purposes of this tool the packages we would
> > track are docker.io-app, containerd-app and runc. I'll update the
> > config to show these three.
> >
>
> Thanks. Ideally, I want to update the container stack every month (if there
> are new upstream releases available), my ongoing work is the foundation to
> allow me to do that. Right now, it is kind of impossible to do it so often
> due to breakages in the archive. Hopefully, next cycle things will be
> better.
Sure. Currently the configuration has a quartly schedule listed, i.e.:
'update-schedule': ['Feb', 'May', 'Aug', 'Nov'],
If you find there's too few cards for you on the board for your tracking
purposes, just let me know what frequency you prefer.
And of course like with merge/sync cards you can also add more mre cards
manually as desired. The only required magic is to subscribe
'canonical-server' and tag the bug 'needs-mre-backport', and then set
the milestone as desired.
Bryce
--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
