[Ksummit-discuss] [CORE TOPIC] stable workflow
Jan Kara
jack at suse.cz
Thu Aug 4 14:02:32 UTC 2016
On Wed 03-08-16 23:25:43, Jiri Kosina wrote:
> On Wed, 3 Aug 2016, Dmitry Torokhov wrote:
>
> > I wonder if we could change meaning of naked cc: stable@ to mean latest
> > stable only, and if fix is important enough then maintainer or somebody
> > else can annotate how far back the fix should be applied? Ideally with
> > "Fixes: XXX"?
>
> Yeah, James already proposed that and I totally agree with that.
>
> Greg, would you have any objection to formulating some rule a-la "all the
> stable anotations should either be accompanied by explicit 'Fixes:', or
> explicit range of kernel versions the patch is applicable to"?
>
> I believe this is a very reasonable compromise between "maintainers or
> submitters have to do their homework wrt. stable" and "we don't want to
> impose too much overhead to anybody".
Yeah. What I like about this proposal is that it is a constant burden per
patch rather than per patch per stable tree (so I as a maintainer /
developer don't have to care how many stable trees are out there). So IMHO
this has a chance to work.
Honza
--
Jan Kara <jack at suse.com>
SUSE Labs, CR
More information about the Ksummit-discuss
mailing list