Hi Kevan/Joe, yes GERONIMO-3966 has been classified as a show-stopper for GEP
2.1, but I "think" we were assuming the problem was in the GEP and not the
server itself. However, it's apparently been a long-term problem in the server,
and is not a windows-only problem, so I'm not certain that it should be
considered a show-stopper for the GEP. Finally, I really wouldn't feel
comfortable propagating it elsewhere until we have clean TCK run against it
since it involves a change in the geronimo-kernel module. Thanks.
Kevan Miller wrote:
On Apr 21, 2008, at 9:09 AM, Joe Bohn wrote:
Shiva,
The same answer applies here that I just sent to Gianny. I've
included it here as well just so that you don't have to go hunting....
branches/2.1.1 is closed to new changes beyond those which would
prevent us from shipping. I had intended to have images up for vote a
few days ago, but I'm having some difficulty creating those images.
They will hopefully be out for a vote later today.
You should include these changes in branches/2.1 (which has been
updated for 2.1.2-SNAPSHOT).
Sorry to be hard nosed about cutting the release ... but we have to
cut sometime and are always more more items coming in to include.
Hopefully we can get better at releasing smaller releases with more
frequency and 2.1.2 won't be long off.
Joe,
I totally understand the sentiment. However, I believe that
GERONIMO-3966 has been classified as a must fix problem for the pending
release of GEP 2.1. I'd like to hear from Tim/Shiva/etc whether or not
that's true... If true, I think we need to consider including... If we
do pick it up, we should probably grab Gianny's change...
--kevan
--
Thanks,
Tim McConnell
