/sigh... Bill, you missed the whole point about bugs@ vs dev@. Whatever. I am quite happy to see Joe and Stefan working the issue on the 'Re: trunk/2.4 core output filter is broken' thread and, as usual, working and 'determining the best API solution' with actual code and implementations... and doing so on the dev@ list where it belongs.
On Jan 25, 2012, at 4:07 PM, William A. Rowe Jr. wrote: > On 1/25/2012 2:28 PM, Jim Jagielski wrote: >> Bill, you should know by now that development is done on dev@... >> private@ is "on-list" as well, by your definition. > > Jim, > > You asked for bugs. We gave you bugs. We tracked notes on bugs. /sigh > >> The issue is that 2.4.x is being held up by an issue, which >> is being "discussed" not on dev@, and since it's not a security >> issue, that's not the way we work. > > It was your thread, dude; asked and answered. /sigh > > That bug revealed a more sinister bug, with discussion on dev. /sigh > <Attached Message.eml><Attached Message.eml>
