From: Javier Martinez Canillas <javierm at redhat.com>
To: tpm2@lists.01.org
Subject: Re: [tpm2] tpm2.0-tools: Release 2.1.0 is available
Date: Wed, 02 Aug 2017 12:04:52 +0200 [thread overview]
Message-ID: <d5cb2bea-e9a2-6c20-407a-01418b968f7f@redhat.com> (raw)
In-Reply-To: 476DC76E7D1DF2438D32BFADF679FC563EAA7739@ORSMSX103.amr.corp.intel.com
[-- Attachment #1: Type: text/plain, Size: 827 bytes --]
Hello folks,
On 07/24/2017 07:54 PM, Roberts, William C wrote:
> Release 2.1.0 is available at: https://github.com/01org/tpm2.0-tools/releases/tag/2.1.0
>
> v2.1.0 - 2017-7-24
I've some questions about the release process that were not answered by reading
the RELEASE document in the repository (it would be nice to add the answers for
these in the doc as well).
1- What's the expected time after a release for the next branch to be created?
2- What's the expected time after a branch is created for a -rc to be released?
I'm asking because there is a bunch of new stuff and fixes currently in master,
so it would be nice to start thinking on the next release:
$ git lg 2.1.0..master | wc -l
221
Best regards,
--
Javier Martinez Canillas
Software Engineer - Desktop Hardware Enablement
Red Hat
next reply other threads:[~2017-08-02 10:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 10:04 Javier Martinez Canillas [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-09-26 20:09 [tpm2] tpm2.0-tools: Release 2.1.0 is available Javier Martinez Canillas
2017-09-25 22:28 Philip Tricca
2017-09-22 11:26 Javier Martinez Canillas
2017-08-16 9:45 Javier Martinez Canillas
2017-08-14 19:38 Roberts, William C
2017-08-10 14:43 Javier Martinez Canillas
2017-07-24 17:54 Roberts, William C
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=d5cb2bea-e9a2-6c20-407a-01418b968f7f@redhat.com \
--to=tpm2@lists.01.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