The range should simply skip 3.0alpha1 and 2
--Brian (mobile)
On Jan 29, 2009, at 12:45 AM, Arnaud HERITIER <[email protected]>
wrote:
What i understand in brett's email is that its patches are for 2.1
branch
but he would like to add ITs to check those fixes in 2.1. His
question seems
to be if he has to activate those ITs for 3.0 also ?
Personnaly I would say yes but perhaps not now if you are preparing an
alpha2. Perhaps it can be a task to fix in alpha3 ?
On Thu, Jan 29, 2009 at 5:28 AM, Jason van Zyl
<[email protected]> wrote:
On 28-Jan-09, at 6:28 PM, Brett Porter wrote:
Hi,
I'm just committing a bunch of fixes. Each has the corresponding
integration test, but since some were in profiles, for example, I
haven't
attempted to merge anything to trunk.
Please don't push anything to trunk, I'll pull in anything in the
alpha-3.
We're about to cut the alpha-2.
Any opinions on how to set the version in the IT? Should it stop at
2.99.99 and come back to check later, or leave it open to include
3.0 and
work to apply them?
Cheers,
Brett
--
Brett Porter
[email protected]
http://blogs.exist.com/bporter/
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
Three may keep a secret if two of them are dead.
-- Benjamin Franklin
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Arnaud
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]