From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============2201517142354560237==" MIME-Version: 1.0 From: Javier Martinez Canillas Subject: Re: [tpm2] tpm2.0-tools: Release 2.1.0 is available Date: Wed, 02 Aug 2017 12:04:52 +0200 Message-ID: In-Reply-To: 476DC76E7D1DF2438D32BFADF679FC563EAA7739@ORSMSX103.amr.corp.intel.com List-ID: To: tpm2@lists.01.org --===============2201517142354560237== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable 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/rele= ases/tag/2.1.0 > = > v2.1.0 - 2017-7-24 I've some questions about the release process that were not answered by rea= ding 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 creat= ed? 2- What's the expected time after a branch is created for a -rc to be relea= sed? I'm asking because there is a bunch of new stuff and fixes currently in mas= ter, 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 --===============2201517142354560237==--