> > > RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP: > > > + > > > + * With AP_MODE_EXHAUSTIVE in the core, it is finally clear to > me > > > + how the Perchild MPM should be re-written. It hasn't worked > > > + correctly since filters were added because it wasn't > possible to > > > + get the content that had already been written and the socket > at > > > + the same time. This mode lets us do that, so the MPM can be > > > + fixed. > > > > > > > -1 on an MPM rewrite until after 2.0 GA is released > > Huh!?!?!?!? You can't veto fixing code that doesn't work. Even more, > you can't veto work that somebody wants to do. The whole point of Open > Source is that we all get to do what is most interesting to us. > > I am fairly confidant in saying that I want to see a GA release more > than anybody else here, except for possibly Bill Stoddard, because the > two of us have been working on 2.0 for longer than anybody else on this > list. However, this push for GA regardless of quality or how fun the > project is really makes me wish that we weren't nearly so close to one. > :-(
BTW, the use of vetos on this list is completely against the way things should be. We use vetos now as an offhanded way of saying that we don't like something, which isn't how they are meant to be used. A veto is basically telling somebody that their approach to a solution is wrong, and that it will break other code, or not scale, or that you have a better way of doing it. They should be rare, and they should only EVER happen with a valid technical justification. I think we have had ten vetos in the last few weeks, which is a lot more than we should have had. I know that there are people on the list who will laugh that I am the person saying this, as I used to use vetos a lot, and sometimes in the wrong places. Chalk that up to being young, inexperienced, and cocky. Vetos are annoying, and they stop the code from progressing forward as it should, please, let's go back to using them sparingly, and only when there is code that is egregiously wrong. Ryan
