On Thursday 29 March 2007 13:05, Nicholas Clark wrote: > I don't think that the stable/development spit in Perl 5 land is broken. > There is a problem that there aren't enough people with good enough > knowledge to be committers, and in particular to want to review and apply > patches supplied by non-committers, which are often for areas that no-one > is totally comfortable with. [Also, there are patches that turn out to be > "works for me" whereas really for something as widespread and production > critical as Perl 5 you want "I understand this code, and this is the right > way to solve it" patches] > > Slightly detached from this is that very few people want to diagnose or fix > bugs. (Which is a job, rather than fun, unless your sense of fun is > somewhat puritanical*). You don't need commit access for this.
Okay, if not broken it's slightly bent. > > <chromatic> When smokes fail, Paul Cochrane fixes a bunch of > > whitespace issues. > > Why do smokes fail? Sometimes there are platform-specific problems. > Are people committing things without running make test? Not me, but I can't speak for everyone. > If I arrange to kidnap Paul Cochrane, will it force a proper solution? :-) More likely, we'll learn to live with more broken windows. > > <allison> I'm totally on board for improving our smoke system > > Most Perl 5 smoke systems report the bad tidings of black smoke to > perl5-porters. I've never noticed a failing Parrot smoke report to this > list, so I infer that they aren't set up this way. Would changing that help > focus minds? That's the plan. > > <particle> and i'm not interested in testing every revision, > > when so many might be coding standards > Why are people even checking things in that fail coding standards? The line-ending coding standards tests can be a problem in some cases, where Windows developers add new files with their native format and forget to set the svn:eol-style=native property on the files, so those standards fail on Unix and Unix-like platforms. I honestly thought we had a little program that added files, updated the MANIFEST appropriately, and set the right properties, but I can't find it anymore. I know I've written that program for a handful of projects already anyway. As for the rest, I can't speculate. -- c
