From: David Marchand <david.marchand@6wind.com>
To: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Cc: Luca Boccassi <bluca@debian.org>, dpdk stable <stable@dpdk.org>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-stable] [PATCH] update step 5.5 in regard to tag/tarball/web handling
Date: Fri, 7 Sep 2018 11:07:47 +0200 [thread overview]
Message-ID: <CALwxeUt6SQKz1Q=z31BVM8k66yQA2iDyy+mAKLsHCiPpOaaCDg@mail.gmail.com> (raw)
In-Reply-To: <20180907053350.10919-1-christian.ehrhardt@canonical.com>
On Fri, Sep 7, 2018 at 7:33 AM, Christian Ehrhardt
<christian.ehrhardt@canonical.com> wrote:
> Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
> ---
> README | 22 ++++++++++++++++++++--
> 1 file changed, 20 insertions(+), 2 deletions(-)
>
> diff --git a/README b/README
> index 8d37403..8d1ceda 100644
> --- a/README
> +++ b/README
> @@ -118,8 +118,26 @@ I haven't write a script for that. But the two have to be done before
> we making a formal release. Thus, this section is titled 5.5.
>
> Git push to dpdk-stable remote will trigger the dpdk host server to generate
> -the release tar package. It will return a md5sum in the end, which is needed
> -to update the dpdk-web.
> +the release tar package.
> +Be careful to push the branch first and only then the tag (or both at once),
> +otherwise some server side automations might silently fail to update properly.
> +
> +This will return a md5sum in the end, which is needed to update the dpdk-web.
> +Example:
> + remote: MD5 (to copy in HTML page)
> + remote: 5e278012506c76d981e4283a92adec1c /srv/rel/dpdk-18.05.1.tar.xz
> +
> +You want to prepiare a change to the DPDK-web, so grab their repository.
My two cents.
s/prepiare/prepare/
> + $ git clone git://dpdk.org/tools/dpdk-web
> +
> +Modify the file content/download/_index.md
> + - update the tarball name
> + - check that the link to the documentation really has your tag listed
> + at the top left
> + - check that the downloadable tarball matches the md5 listed on the
> + git push output
> + - add that new md5 to the file
> +and finally suggest that change to the web team at web@dpdk.org
--
David Marchand
next prev parent reply other threads:[~2018-09-07 9:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 5:33 Christian Ehrhardt
2018-09-07 9:07 ` David Marchand [this message]
2018-09-07 9:19 ` Luca Boccassi
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='CALwxeUt6SQKz1Q=z31BVM8k66yQA2iDyy+mAKLsHCiPpOaaCDg@mail.gmail.com' \
--to=david.marchand@6wind.com \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).