04/07/2018 17:22, Thomas Monjalon:
> 30/06/2018 01:10, Kevin Traynor:
> > Set the starting point that all commits on master branch
> > with Fixes tag should be backported to relevant stable/LTS
> > branches, and explain that the submitter may indicate it is
> > not suitable for backport.
> >
> > Of course there will be exceptions that will crop up from time
> > to time that need discussion, so also add a sentence for that.
> >
> > This is to ensure that there is consistency between what is
> > backported to stable/LTS branches, remove some subjectivity
> > as to what constitutes "a fix" and avoid possible conflicts
> > for future backports.
> >
> > Signed-off-by: Kevin Traynor <ktray...@redhat.com>
> > Acked-by: Luca Boccassi <bl...@debian.org>
> > Acked-by: Aaron Conole <acon...@redhat.com>
> > ---
> > -Backporting should be limited to bug fixes.
> > +Backporting should be limited to bug fixes. All patches accepted on the
> > master
> > +branch with a Fixes: tag should be backported to the relevant stable/LTS
> > +branches, unless the submitter indicates otherwise. If there are
> > exceptions,
> > +they will be discussed on the mailing lists.
> > +
> > +Fixes suitable for backport should have a ``Cc: sta...@dpdk.org`` tag in
> > the
> > +commit message body as follows::
> > +
> > + doc: fix some parameter description
> > +
> > + Update the docs, fixing description of some parameter.
> > +
> > + Fixes: abcdefgh1234 ("doc: add some parameter")
> > + Cc: sta...@dpdk.org
> > +
> > + Signed-off-by: Alex Smith <alex.sm...@example.com>
> > +
> > +
> > +Fixes not suitable for backport should not include the ``Cc:
> > sta...@dpdk.org`` tag.
>
> Acked-by: Thomas Monjalon <tho...@monjalon.net>
>
> The technical board reviewed it and approve this clarified guideline.
Applied, thanks
