patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Luca Boccassi <bluca@debian.org>, dpdk stable <stable@dpdk.org>
Cc: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Subject: [dpdk-stable] [PATCH] Readme: clarify that rc tag will be created by step 4
Date: Wed, 22 Aug 2018 09:33:17 +0200	[thread overview]
Message-ID: <20180822073317.17185-1-christian.ehrhardt@canonical.com> (raw)

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

             reply	other threads:[~2018-08-22  7:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-22  7:33 Christian Ehrhardt [this message]
2018-08-22 10:13 ` 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=20180822073317.17185-1-christian.ehrhardt@canonical.com \
    --to=christian.ehrhardt@canonical.com \
    --cc=bluca@debian.org \
    --cc=stable@dpdk.org \
    /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).