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

On Sat, Dec 3, 2016 at 3:56 PM, Hahnfeld, Jonas
<Hahnfeld at itc.rwth-aachen.de> wrote:
> 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@ -

>
>> -----Original Message-----
>> From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of
Sedat
>> Dilek via llvm-dev
>> Sent: Saturday, December 03, 2016 2:12 PM
>> To: Tom Stellard
>> Cc: llvm-dev
>> Subject: [llvm-dev] 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/
>> _______________________________________________
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

> -----Original Message-----
> From: Sedat Dilek [mailto:sedat.dilek at gmail.com]
> Sent: Saturday, December 03, 2016 5:24 PM
> To: Hahnfeld, Jonas
> Cc: Tom Stellard; llvm-dev (llvm-dev at lists.llvm.org)
> Subject: Re: [llvm-dev] Tarballs for 3.9.1rc2 pre-release
>
> On Sat, Dec 3, 2016 at 3:56 PM, Hahnfeld, Jonas <Hahnfeld at itc.rwth-
> aachen.de> wrote:
> > 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
>
> 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@ -
>
>
> >
> >> -----Original Message-----
> >> From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On
Behalf Of
> >> Sedat Dilek via llvm-dev
> >> Sent: Saturday, December 03, 2016 2:12 PM
> >> To: Tom Stellard
> >> Cc: llvm-dev
> >> Subject: [llvm-dev] 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/
> >> _______________________________________________
> >> LLVM Developers mailing list
> >> llvm-dev at lists.llvm.org
> >> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5868 bytes
Desc: not available
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20161203/4a8e2841/attachment-0001.bin>

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