[dpdk-stable] [PATCH] update step 5.5 in regard to tag/tarball/web handling

[David Marchand]

On Fri, Sep 7, 2018 at 7:33 AM, Christian Ehrhardt
<christian.ehrhardt at canonical.com> wrote:
> Signed-off-by: Christian Ehrhardt <christian.ehrhardt at 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 at dpdk.org


-- 
David Marchand