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.> 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 2.5 and 2.6 releases, so, one should definitely expect to see another one for 2.7. 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? -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University
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 forNope. 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. -Dave
On Wednesday 07 April 2010 13:44:44 David Greene wrote:> > 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 don't see it in the gmane archives but that doesn't matter. Looking back at those archives, I recall that I was in the middle of iterating on a patch to add some debug capability to LLVM. I was focused on that and could easily miss a bug reference like that. I wasn't focusing on the 2.7 release at the time, quite frankly. 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. I can't say I would have been able to devote loads of time to fixing bugs at that point (I could have helped a bit, I'm sure) but having the information out there and accessible (linked from the project home page, etc.) would help many people to get involved. -Dave
>> 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?In pretty secret place! llvmdev & cfe-dev mailing lists. See http://lists.cs.uiuc.edu/pipermail/llvmdev/2010-March/030270.html for example> 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.It is. See http://lists.cs.uiuc.edu/pipermail/llvmdev/2010-March/030574.html as an example. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University