Hi Jason,
On Feb 15, 2007, at 3:55 PM, Jason van Zyl wrote:
Hi,
So that no one can accuse of resting on our laurels time to start
planning for 2.0.6. Not sure what the best way is to gather the
issues to work on but it would be nice to gather them in the next
week or so, and then work the next three weeks to resolve them and
do another release in 4 weeks.
Awesome!
We can try the voting thing like we do with the plugins, or people
can bring up issues and it's first come first serve. You can pick
from here:
http://jira.codehaus.org/secure/IssueNavigator.jspa?
reset=true&&pid=10500&resolution=-1&fixfor=13141&sorter/
field=priority&sorter/order=DESC
Or if you know that an issue has been the wrong fix version tell us.
These are the issues I'm interested in:
MNG-1412
MNG-624
MNG-2653
MNG-1949
MNG-2823
Project with full test cases that can be easily absorbed will be
taken before anything else anything else. If these are for fixes
and you have unit tests that's great, or if you prefer to create an
integration test then to make this easier I have created a self-
contained, fully working of example of our integration tests:
http://svn.apache.org/repos/asf/maven/core-integration-testing/
trunk/core-integration-test-sample
or
http://idisk.maven.org/jvanzyl/Public/maven-integration-tests/core-
integration-test-sample.zip
I'm a bit confused. This looks considerably different than what I see
in maven-core-it. The ones in maven-core-it look pretty straight
forward. Are there examples of this new style in the maven-2.0.x
tree? If we use this new style, how do you want us to submit the test
(assuming it won't be part of the patch)?
Anyone who produces an integration using this form I guarantee your
patches will go to the front of the line. I know that many people
contribute time to fix things and are frustrated when we don't
apply patches, but it also very frustrating for us to try and piece
together comments and bits of code cobbled together in JIRA. I'm
hoping that this will help. Our integration testing strategy is not
fully fleshed out but what's in that example is what we are using
today and them being all the same as we can move them all forward
together when we improve it.
Even for issue where you don't have a solution providing a test
where we can at least accurately reproduce the problem is immensely
helpful. I will make an archetype of this example but I wanted to
get this mail out to get the ball rolling for 2.0.6 so you can take
the svn checkout or the zip.
I have not forgotten about poor MNG-1577 :-)
Jason.
Cheers,
Eric
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
