personally, I am trying to make the master tree as clean as possible, a clean tree is very important for new comers, when they can feel happy with the way we pushing the project, I'd like every one love this project, for using and coding everyday.
Well, we make big changes when it really ought to, but that should not turn into "do what ever you want at anytime". That is why we call us a community and a community project, I really wish we can work as a team, even we don't know each other "face to face". We work for fun, we need feel nice with the codes, and the man behind the codes :D Big project as ATS, I think no none is able to all the parts, we believe that we can work together so we can manage the big ship. For ATS project, I always think that we don't need run in a hurry, we are the most powerful system in the world, no one is able to kill us in this field, we have a big & healthy community support, what we aught to do is make it better in stabilization & performance, we are high performance critical system that we can even persuade the user choose the right hardware and operation system as we suggest, just "because it sucks less!" I am managing the small community in China, where I was always asked by 'why mt ats is crashing', I have to tell them: 1, do not enable Range in v3.2.0 2, do not use the CLFUS, use the standard LRU 3, do not use the thread pool to manage server sessions ...... at last, try my tree if you are not satisfied with the official tree, it is proved to be working well with 10 thousands of queries per second. I am not happy with that, because I working for the community, just because we can not control the quality of our official releases. The quality is build from everyday coding, everyone thinking. we really should care of it. fin, I have wrote too much, that don't like me as common. I'd wish my words not hurt anyone here. thanks, you are my best partner! 在 2012-11-22四的 11:26 -0500，Leif Hedstrom写道： > On 11/21/12 12:35 PM, James Peach wrote: > > On 21/11/2012, at 9:32 AM, James Peach <jpe...@apache.org> wrote: > > > >> > >> This change makes merging "upstream" changes for him much more > >> difficult. Before I revert this commit again, I'd like to > >> bring this to attention, because: > >> > >> trunk is CTR, and I'd like to keep it that way. > >> > >> There's a number of options we have from here, and I'd really > >> like we figure this out now. > >> Obviously I did not test this on GCC 4.7 like I should have. > > Oh, and when people (like me) commit breaking changes like this we should > > feel comfortable with just reverting them IMHO ... > > Yeah, I think we should nuke it for now. > > A big change, such as changing which C++ standard we conform to in our > builds, ought to be discussed on the mailing lists I think? I know we > made it configure optional, and that's fine, but apparently there are > serious side effects :). > > Cheers, > > -- Leif > > > -- Zhao Yongming aka: zym @ apache.org, yonghao @ taobao.com
