On 2009-11-14, at 4:47 AM, Dan Fabulich wrote:


I was waiting until alpha-3 was out to merge in the MNG-3004 branch. MNG-3004 passes all ITs, including a few new ITs of the experimental multithreaded mode.

Can we recut alpha-4 with MNG-3004 in it?


I'd personally still like to see a little more design around the multi- threading first. We are going to roll out alpha after alpha based on feedback we get from users to fix common problems first. I think that is the real priority we have. I honestly do not see the urgent rush to push this is. If we have fixes for users I want to push those out first. I want to be cautious about new features. We haven't added any new features to the core yet. I have 5-10 things on git branches but I just don't think it's the priority.

Honestly there's not really any public proposal or design to look at, and I really think that we should try your branch against the performance framework and make sure everything is ok. I'm not just doing this with your feature, I've done it with all the ones that I have. I've refrained from putting in because I want to make sure we don't ever go backward and I don't think there is anything wrong with erring on the side of caution and waiting a couple weeks.

We'll probably keep doing 1-2 alphas a week so there isn't going to be a huge time span you have to wait. I think we need a proposal and I think that we have to get into the habit of having two other people review new features at a bare minimum. I don't think this is an unreasonable approach.

-Dan


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
----------------------------------------------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to