Tarballs for 3.9.1rc2 pre-release

Hi Tom,

[1] does not list any 3.9.1rc2 pre-release tarballs, can you please upload?

Thanks in advance.

Regards,
- Sedat -

[1] http://www.llvm.org/pre-releases/

Hi Sedat,

as already said multiple times for the past releases: The tarballs will be
uploaded once they are finished. The tagged version currently gets tested
which is done with an export from SVN AFAIK.

Please just be patient and give the process some time,
Jonas

Hi Sedat,

as already said multiple times for the past releases: The tarballs will be
uploaded once they are finished. The tagged version currently gets tested
which is done with an export from SVN AFAIK.

Please just be patient and give the process some time,

With the announcement the tarballs should be uploaded - that's the
usual workflow in all OSS projects I know.

What do you want to tell me.. You announce before testing?
RCs are for testing - really strange :-).

You should do testers the life easy not hard.

In the meantime I updated my local Git repositories, extracted
source-tarballs my own and built my llvm-toolchain.
...and will do my usual testcase building a Linux-kernel v4.4.y-LTS.

- sed@ -

From: Sedat Dilek [mailto:sedat.dilek@gmail.com]
Sent: Saturday, December 03, 2016 5:24 PM
To: Hahnfeld, Jonas
Cc: Tom Stellard; llvm-dev (llvm-dev@lists.llvm.org)
Subject: Re: [llvm-dev] Tarballs for 3.9.1rc2 pre-release

> Hi Sedat,
>
> as already said multiple times for the past releases: The tarballs
> will be uploaded once they are finished. The tagged version currently
> gets tested which is done with an export from SVN AFAIK.
>
> Please just be patient and give the process some time,

With the announcement the tarballs should be uploaded - that's the usual
workflow in all OSS projects I know.

What do you want to tell me.. You announce before testing?
RCs are for testing - really strange :-).

I think you got that wrong: Tom announced the tagging, not the availability of
the release candidate.
Please have a look at how the same thing happened for 3.9.0 and we tried to
explain that to you back then...

Regards,
Jonas

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

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

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