On 09/25/2017 12:34 PM, Christian Boltz wrote: > Hello, > > the forwarded bug comment below says it all - we should do maintenance > releases for 2.11, 2.10 and 2.9 ASAP ;-) > yes, I'll try to get something out this week.
Realistically we should have a regular release schedule planned, where we skip a release if there are no changes. I will add it to the agenda for the meeeting in August, which we will have. > 18 cherry-picked patches in Debian are one reason. > > The other reason is that I also carry several patches in the openSUSE > package already - including two of my infamous "upstream-changes- > rXXX..YYY.diff" which cover a total of 30 revisions - and miss another > 30 revisions from the 2.11 branch. > > > From the openSUSE POV, I need 2.10.x and 2.11.x. None of the maintained > openSUSE releases uses 2.9.x anymore, and SLE12 still enjoys ;-) 2.8.x > with quite some backported patches. > > Are there distributions that still use 2.9? If not, I'd still do a last > 2.9.x release (we did the backporting to 2.9 already, so creating a > tarball is cheap) and at the same time declare the 2.9 branch as no > longer maintained. (If a distribution still uses 2.9.x, keeping it > maintained isn't too hard - I just want to avoid doing work for nobody.) > > > ---------- Forwarded Message ---------- > > Subject: Re: [Bug 1719195] Re: aa-logprof: apparmor.common.AppArmorBug: > Passed unknown <class 'NoneType'> object to PtraceRule: None > Date: Monday, September 25th 2017, 08:47:56 CEST > From: intrigeri > > Vincas Dargis: >> OK thanks, I'll nudge Debian maintainer then :) > > Well, a new upstream release would be welcome: we're already applying no > less than 18 patches cherry-picked from upstream bzr or from fixes > submitted for review upstream already. > > > -- AppArmor mailing list AppArmor@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/apparmor
