[dpdk-stable] [PATCH] Readme: clarify that rc tag will be created by step 4

[dpdk-stable] [PATCH] Readme: clarify that rc tag will be created by step 4

[Christian Ehrhardt]

Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
---
 README | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/README b/README
index 8a2ccea..06f4be5 100644
--- a/README
+++ b/README
@@ -87,6 +87,12 @@ that we are going to have following commits for a stable/LTS release.
 Do you have more comments, something like this commit should be removed,
 or something are missing, etc.
 
+This will also create a tag like v18.05.1-rc1 for you.
+Before sending this mail you might want to make a RC tarball available.
+To get that push the tag to the repository, hooks will generate a tarball.
+The generated link in the mail to the tag will not only show the tag,
+but also have links to the tarballs.
+
 The usage is simple, just time the command, it then will generate an
 email with the notification content. What you need to so it to edit it
 when necessary (say, leaving more time for review) and send it out.
-- 
2.17.1

Re: [dpdk-stable] [PATCH] Readme: clarify that rc tag will be created by step 4

[Luca Boccassi]

On Wed, 2018-08-22 at 09:33 +0200, Christian Ehrhardt wrote:
> Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
> ---
>  README | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/README b/README
> index 8a2ccea..06f4be5 100644
> --- a/README
> +++ b/README
> @@ -87,6 +87,12 @@ that we are going to have following commits for a
> stable/LTS release.
>  Do you have more comments, something like this commit should be
> removed,
>  or something are missing, etc.
>  
> +This will also create a tag like v18.05.1-rc1 for you.
> +Before sending this mail you might want to make a RC tarball
> available.
> +To get that push the tag to the repository, hooks will generate a
> tarball.
> +The generated link in the mail to the tag will not only show the
> tag,
> +but also have links to the tarballs.
> +
>  The usage is simple, just time the command, it then will generate an
>  email with the notification content. What you need to so it to edit
> it
>  when necessary (say, leaving more time for review) and send it out.

Thanks, applied and pushed

-- 
Kind regards,
Luca Boccassi