[LLVMdev] Call for Help: Testing

Chandler Carruth chandlerc at google.com
Wed Apr 7 13:36:28 PDT 2010

On Wed, Apr 7, 2010 at 11:44 AM, David Greene <dag at cray.com> wrote:

> On Wednesday 07 April 2010 12:53:48 Anton Korobeynikov wrote:
> > Hi, David
> >
> > > To say that "It can't be the same people fixing the bugs for every
> > > release" discounts a lot of good, hard work put in by a lot of people.
> > > There wasn't a lot for "the community" to do before late last week
> except
> > > run tests, which in fact a number of people did.
> >
> > Why? Prerelease 1 tarballs are available for at least 3 weeks. PR6623
> > was entered into bugzilla at March, 20, etc., etc., etc.
> But where was it posted to let people know about it?

It was posted to the dev mailing lists. In fact, that's the *exact* same
place that your email was posted. How can you claim that this is impossible
or even hard to find, and yet send emails to it expecting people to find,
read, and take action based on them? (Remember, your subject line was 'Call
for help'...)

> > > Did I miss an announcement of PR6586 somewhere?  The first I knew about
> > > it was mid last week.  Maybe I missed the posting on this mailing list
> > > about it. It's been open for almost a month.  Without knowing about
> that
> > > bug, it's pretty tough for people to do anything about it.
> >
> > It's pretty strange to hear about this from you. I hoped everyone who
> > worked with llvm for some non-trivial period of time knows about
> > "master" bug habits in the LLVM bugzilla. Such bugs were created for
> Nope.  I've seen master bugs with other projects, but I don't see
> anything on the LLVM website to direct me.

Seriously? http://www.lmgtfy.com/?q=llvm+2.7+release+master+bug

1st link: the gmane archive you claim to have looked at, with the bug number
in the snippet
4th link: the bugs mailing list email noting the creation of the bug, with
all of its contents and a link to bugzilla

I hadn't seen those bugs.  And even if I had, what about newer people?
> > Also, I should note that master bug in question was *explicitly*
> > mentioned in Tanya's 2.7 prerelease 1 e-mail sent on March, 17.
> > Have you seen this e-mail?
> Hmm, I'm sure I got it.  I must have missed it.  I can't read the list
> every day and after a few days things get pretty backed up.

I'm not sure why you think burying links that are only relevant for a narrow
window of time in a long-lived webpage is more discoverable than email.
Also, unless you are subscribed to the commit list, the load from llvmdev is
very modest.

On Wed, Apr 7, 2010 at 11:52 AM, David Greene <dag at cray.com> wrote:

> On Wednesday 07 April 2010 13:44:44 David Greene wrote:
I don't see it in the gmane archives but that doesn't matter.

I find this hard to believe. Did you really look? There are exactly two
links in the email, one of them to the bug. Let's use the fancy powers of
search to help out:

People are going to miss e-mails.  That's a fact of life.
> Perhaps weekly status updates with tracking bug number after the release
> branch is made would be helpful, along with daily updates as we get
> closer to the scheduled release date.

The solution to people not reading email is not to send them more email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100407/0f783348/attachment.html>

More information about the llvm-dev mailing list