[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH v2 2/2] docs/process/xen-release-management: Lesson to learn




On 22/05/2018, 12:45, "Ian Jackson" <ian.jackson@xxxxxxxxxxxxx> wrote:
    
    CC: Lars Kurth <lars.kurth@xxxxxxxxxx>
    CC: Julien Grall <julien.grall@xxxxxxx>
    Acked-by: Juergen Gross <jgross@xxxxxxxx>
    Signed-off-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
    ---
     docs/process/xen-release-management.pandoc | 5 +++++
     1 file changed, 5 insertions(+)
    
    diff --git a/docs/process/xen-release-management.pandoc 
b/docs/process/xen-release-management.pandoc
    index 2ff0665..eee5dcf 100644
    --- a/docs/process/xen-release-management.pandoc
    +++ b/docs/process/xen-release-management.pandoc
    @@ -211,6 +211,11 @@ https://wiki.xenproject.org/wiki/Category:Xen_4.9
         Ask them to dry-run their checklist and confirm everything is OK. If 
not,
         arrange another RC and restart this checklist.
     
    +7. Do not commit to a release date until
    +
    +    * The exact xen.git commit id to be released is known.
    +    * That commit id has been satisfactorily tested.
    +
     7. Give PR Personnel final go-ahead, and instruct Release Technician to 
make
     release deliverables (tags and tarballs - will usually be in place the day
     before the release). At this point, PR collateral will be sent to reporters

Acked-by: Lars Kurth <lars.kurth@xxxxxxxxxx>
    

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.