Re: [Xen-devel] [PATCH] Introduce a description of a new optional tag for Backports

[Stefano Stabellini <sstabellini@xxxxxxxxxx>]

On Mon, 11 Nov 2019, Lars Kurth wrote:
> On 11/11/2019, 08:12, "George Dunlap" <george.dunlap@xxxxxxxxxx> wrote:
> 
>     On 11/8/19 7:09 PM, Stefano Stabellini wrote:
>     > Signed-off-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxx>
>     > CC: jbeulich@xxxxxxxx
>     > CC: george.dunlap@xxxxxxxxxx
>     > CC: julien@xxxxxxx
>     > CC: lars.kurth@xxxxxxxxxx
>     > CC: andrew.cooper3@xxxxxxxxxx
>     > CC: ian.jackson@xxxxxxxxxxxxx
>     > CC: konrad.wilk@xxxxxxxxxx
>     > CC: wl@xxxxxxx
>     > ---
>     >  docs/process/backport-tag.pandoc | 23 +++++++++++++++++++++++
>     >  1 file changed, 23 insertions(+)
>     >  create mode 100644 docs/process/backport-tag.pandoc
>     > 
>     > diff --git a/docs/process/backport-tag.pandoc 
> b/docs/process/backport-tag.pandoc
>     > new file mode 100644
>     > index 0000000000..e570efdcc8
>     > --- /dev/null
>     > +++ b/docs/process/backport-tag.pandoc
>     > @@ -0,0 +1,23 @@
>     > +Backport Tag
>     > +------------
>     > +
>     > +A backport tag is an optional tag in the commit message to request a
>     > +given commit to be backported to the stable trees:
>     > +
>     > +    Backport: all
>     > +
>     > +It marks a commit for being a candidate for backports to all relevant
>     > +trees.
>     > +
>     > +    Backport: 4.9+
>     > +
>     > +It marks a commit for being a candidate for backports to all stable
>     > +trees from 4.9 onward.
>     > +
>     > +Maintainers request the Backport tag to be added on commit.
>     > +Contributors are also welcome to mark their patches with the Backport
>     > +tag when they deem appropriate. Maintainers will request for it to be
>     > +removed when that is not the case.
>     > +
>     > +Please note that the Backport tag is a **request** for backport, which
>     > +will still need to be evaluated by the stable tree maintainers.
>     
>     The text and the idea both look good to me.

Thank you!


>     But it seems kind of balkanized to put it in its own file.  Would it be
>     better to try to make a slightly more general bit of content?  Either
>     about the backport process, or about tags in general?

Yeah, it was never meant to stay in its own separate file. I thought it
would get merged into a bigger file about the whole process when it gets
submitted.


> It should be in 
> https://wiki.xenproject.org/wiki/Submitting_Xen_Project_Patches#What_is_in_a_patch.3F
> What is currently missing is
> - Release-Acked-by
> - The new proposed tag 
> 
> But maybe we should have a master document in tree, which defines the tags in 
> use
> And then I can refer to it from 
> https://wiki.xenproject.org/wiki/Submitting_Xen_Project_Patches#What_is_in_a_patch.3F
>  

For now, would you like me to add the text to the wiki at
https://wiki.xenproject.org/wiki/Submitting_Xen_Project_Patches#What_is_in_a_patch.3F
 ?
Or would you rather do it?

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel