Sorry, I only read the first part of your email. I think the controlling the threads with a setting is a good idea.
I don't see any point in doing another milestone release. The current code is as stable as 2.0.9/10 yet noone can use it because it's a milestone. It serves us no point because we don't get any feedback. The original intent of the milestones was to give the team targets to work towards quickly to get 2.1 out. Since no work was made towards those targets in the last 6 months, we should just cut the release and move on. When a feature appears and is ready with tests, then we can include it and release it. The nature of the oss developent timeline is too haphazard to fully schedule releases like we tried and in the meantime good code sits unused. I think we should fix the minimum bugs that are regressions, clean up what is already there and do a 2.1.0 release asap. Everything else can be 2.2 (features) or 2.1.1 (bugs) On 2/14/09 7:22 AM, "Brett Porter" <[email protected]> wrote: > So, there seems to be some agreement. > > However, I've come back from underground and now there are *two* > snapshots on trunk. I'm already spending valentine's day alone, so I > didn't really need another reason to curl up in the corner and cry :) > > I would really like to pull an M2 release in the next week with the > stuff that is already there. John, what do you think? > > Thanks, > Brett > > On 10/02/2009, at 9:43 AM, Brian E. Fox wrote: > >> Yep good idea. >> >> -----Original Message----- >> From: Brett Porter [mailto:[email protected]] On Behalf Of Brett >> Porter >> Sent: Monday, February 09, 2009 7:44 PM >> To: Maven Developers List >> Subject: Re: Maven 2.1.0 Plans (a proposal of sorts) >> >> >>> >>> I'm +1 for including it and providing an opt-out switch to turn it >>> off. If we can make that switch stick permanently via the >>> settings.xml, so much the better. >> >> +1 (even better, configure number of parallel threads, just set it to >> 1 to turn it off). >> >> On 09/02/2009, at 11:18 PM, John Casey wrote: >> >>> I'll rearrange the JIRA versions today, then...it looks like we're >>> all in agreement about moving directly toward 2.1.0 generally. >>> >> >> Let's slow down a bit... >> >> We are totally in agreement to moving towards 2.1.0 generally, and the >> list in JIRA now reflects that. >> >> However, I don't see why we'd cancel a milestone release when there's >> already been good progress. I was all ready to roll that once the >> remaining snapshot was released (I've been working on it since >> December since you said you didn't have time), but now JIRA has been >> transformed and any release is 23 issues (I'm guessing probably 2 >> weeks minimum) away. Then the RC cycle will be more brutal. >> >> Why couldn't we stick to the plan as it was yesterday? Same issues, >> more intermediate releases. >> >> - Brett >> >> -- >> Brett Porter >> [email protected] >> http://blogs.exist.com/bporter/ >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > -- > Brett Porter > [email protected] > http://blogs.exist.com/bporter/ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
