On 18/02/2009, at 4:58 PM, John Casey wrote:
Brett Porter wrote:
On 18/02/2009, at 7:23 AM, John Casey wrote:
It will take less effort for me to just keep working on issues
until they are done, so that's what I'll do. So, agreed, next
version is 2.1.0, standard RC cycle applies.
I'm fine whittling away some of what's left out there. I don't think
it all has to happen in 2.1.0. IMO, we should take care of the four
top-voted issues if we can - and if we can be relatively sure we're
not angering the gods with our hubris - then do the rest in 2.1.1.
Ok, I dropped a couple of non-controversial ones and assigned some to
self. Some of them have patches so should be quick enough to get in
there.
Beyond that, I'm alright releasing 2.1.0 final provided we can be
sure that the wagon version we're using is stable. I seem to
remember an issue coming up shortly after the release of 2.1.0-M1
related to one of the new Wagon implementations - WebDAV, maybe?
I'm having some trouble remembering/finding that issue in my
gmail, but we need to make sure that doesn't get left out of this
release. If it means rolling back to an older wagon version, then
let's do that.
It's a regression in the SSH wagon, which I've not been able to
reproduce and I never saw an issue filed for. We can wait and see
what happens in the RC cycle.
Do you happen to have a Nabble link for that thread? I'll keep
searching, but it'd be really nice to push that to resolution, as
it's probably the biggest wart on 2.1.0-M1.
I think it's the one from Henrique here:
http://markmail.org/thread/2goikjq2x3nqrx5z
I can fiddle around with it again to see if I can reproduce.
- Brett
--
Brett Porter
br...@apache.org
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
