[LLVMdev] Call for Help: Testing
dag at cray.com
Wed Apr 7 11:44:44 PDT 2010
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?
> > 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. Again, to get volunteers
to help, it has to be as simple as possible for people to figure out
what needs to be done.
This is on all of us. I'm not pointing fingers at anyone in particular.
> 2.5 and 2.6 releases, so, one should definitely expect to see another
> one for 2.7.
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 think it would be good to mention the bug number with every pre-release
related e-mail from the release manager. There's less chance of missing
an important message.
I'm just relating my experience. I got pretty frustrated seeing everyone's
work dismissed as inadequate.
More information about the llvm-dev