From: Wei Liu <wei.liu2@citrix.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com, Wei Liu <wei.liu2@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Tim Deegan <tim@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH] misc/release-checklist: Import from xenbits:~xen/release-checklist
Date: Mon, 5 Dec 2016 13:32:17 +0000 [thread overview]
Message-ID: <20161205133217.GM3522@citrix.com> (raw)
In-Reply-To: <1480941372-16262-1-git-send-email-ian.jackson@eu.citrix.com>
On Mon, Dec 05, 2016 at 12:36:12PM +0000, Ian Jackson wrote:
> This checklist is what we use when releasing, branching, and making
> tarballs. Right I want to commit an exact copy of the live copy kept
> on xenbits outside version control. I am fed up of maintaining this
> outside version control, and probably xen.git is the best place to put
> it.
>
> I have reviewed the contents and while it contains much that might be
> considered embarrassing, it doesn't contain any secrets :-).
>
> I suggest that:
>
> * This file should live in misc/ rather than docs/ on the grounds
> that no-one else is likely to ever want it.
>
> * We maintain the copy in xen.git#staging as the master copy for all
> branches. When things change they are more often changes to
> infrastructure organisation and so on. So the file will continue
> to contain explicit treatment for old Xen branches.
>
> * We will not retain information about branches which are out of
> security support. (So some of what is there can be deleted at our
> leisure.)
>
> * This file will be maintained by the release technicians (currently
> mostly that means me, although others have done some parts of the
> task) and commits will be made by release technicians without
> further review or acks.
>
This looks sensible to me.
> Please argue about the filename :-).
I don't have opinion on this.
Wei.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-12-05 13:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 12:36 [PATCH] misc/release-checklist: Import from xenbits:~xen/release-checklist Ian Jackson
2016-12-05 12:48 ` Jan Beulich
2016-12-05 13:32 ` Wei Liu [this message]
2016-12-07 16:48 ` Ian Jackson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161205133217.GM3522@citrix.com \
--to=wei.liu2@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.