llvm dev - Dec 2016 - Tarballs for 3.9.1rc2 pre-release

On 3 December 2016 at 17:23, Hahnfeld, Jonas via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> I think you got that wrong: Tom announced the tagging, not the availability
of
> the release candidate.
I think the confusing thing here is that the email was sent to
llvm-dev and cfe-dev inviting people to test it.

Maybe we should move to a schedule where the internal testing for the
release candidates is only announced in the release-testers list, and
whenever we all test and upload (and the release manager then moves it
publicly), we announce on the dev lists.

Tom, Hans, would that be a good idea?

Anyone wanting to participate on the internal testing should sign up
for that list anyway. Anyone participating on the public testing can
remain on the dev lists.

cheers,
--renato

On Sat, Dec 3, 2016 at 2:17 PM, Renato Golin <renato.golin at linaro.org>
wrote:
> On 3 December 2016 at 17:23, Hahnfeld, Jonas via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
>> I think you got that wrong: Tom announced the tagging, not the
availability of
>> the release candidate.
>
> I think the confusing thing here is that the email was sent to
> llvm-dev and cfe-dev inviting people to test it.
>
> Maybe we should move to a schedule where the internal testing for the
> release candidates is only announced in the release-testers list, and
> whenever we all test and upload (and the release manager then moves it
> publicly), we announce on the dev lists.
>
> Tom, Hans, would that be a good idea?
I can see your point (and maybe I've sent a few emails that way
myself), but it's also good to keep the wider community informed about
when the tags go in.

I usually use a subject of "Release Candidate foo has been tagged",
which I hope is clear enough. Maybe we should take more care to
explicitly spell out that this is a tag, and the binaries will be
available in a few days.

Cheers,
Hans

On 3 December 2016 at 22:34, Hans Wennborg <hans at chromium.org>
wrote:
> I usually use a subject of "Release Candidate foo has been
tagged",
> which I hope is clear enough. Maybe we should take more care to
> explicitly spell out that this is a tag, and the binaries will be
> available in a few days.
That works, too. A few common subject lines can help, too. It makes
sure people get used to it, and maybe even help filter.

Things like:

"[3.9.1] Release branched"
"[3.9.1] Release candidate N available"

cheers,
--renato