Re: Wheezy update of libtomcrypt?
Thanks for having a look!
On Wed, Sep 07, 2016 at 01:23:49PM +0200, Bálint Réczey wrote:
> 2016-09-07 8:00 GMT+02:00 Guido Günther <firstname.lastname@example.org>:
> > Hi Bálint,
> > On Wed, Sep 07, 2016 at 12:21:28AM +0200, Bálint Réczey wrote:
> >> Hi Michael,
> >> 2016-09-04 17:51 GMT+02:00 Michael Stapelberg <email@example.com>:
> >> > Thanks for your work on LTS.
> >> >
> >> > Time does not permit me to do any of this work myself.
> >> >
> >> > Please go ahead and make any changes as you see fit, there’s no need for my
> >> > review.
> >> Thank you for your quick answer.
> >> I (on behalf of the LTS Team since I'm responsible for frontdesk now) take your
> >> answer as covering all future security updates for releases in LTS period
> >> thus we won't contact you for each CVE.
> > It's great idea to have maintainers actually "opt out" of future mails
> > regarding LTS.
> > Do we keep a list of packages where we don't want to contact maintainers
> > since they don't want to work on LTS updates? Ideally this would be
> > parsed by contact-maintainers.
> I have updated the contact-maintainers template and added an initial list in
> data/packages/lts-do-not-call .
> If the format is OK, we can also update the contact-maintainers script.
Looks o.k. to me. Since we have the tools that read that file and the
file in the same repo we can switch to more complex format at any later
point if necessary.