On Tue, Jul 5, 2011 at 8:51 AM, Hyrum K Wright <hy...@hyrumwright.org> wrote:
>> We want to ship the best product possible. This mailing list is defined to >> be our decision-making focus. It seems incorrect to disregard a reported >> problem simply because (for whatever reason) an issue is not in the tracker. > > I don't claim that we should disregard the problem. I *do* claim that > we should more widely publicize blocking issues so that everybody can > be aware of them. > > The greater point was that this seems to be something that various > people have kicking around in their heads. We agreed in Berlin (and > then discussed on this list) to use the issue tracker to record > blocking issues. I really don't want to be in the position of rolling > a possible release candidate, only to find out we're got all these > hidden issues that aren't being tracked in the agreed-upon public > manner. I am with Hyrum on this one. If there are blockers people need to create issues for them or at least formally raise them on dev@ so that someone else can create an issue. We should not be waiting for Hyrum to announce the plans to make a release to suddenly reveal there are blockers. I do not think Hyrum was being flippant, I think he was basically saying "how am I supposed to know there are blockers if you wait to tell me when I announce plans for the release?" Anyway, from what I see this still has not been entered in the issue tracker. Also, if Bert seems to have a fix for the problem why are we not just putting that in place? I do not get the "waiting for Ivan" part. Is there anything blocking Ivan from making the fix a better/different way if he finds the time? -- Thanks Mark Phippard http://markphip.blogspot.com/
