On Jan 22, 2006, at 5:58 PM, David Jencks wrote:
On Jan 20, 2006, at 1:33 PM, Dain Sundstrom wrote:
I am working on splitting the OpenEJB container into one object
for each deployed ejb and a set of share invocation processing
ejb containers. This is a refactoring of internal interfaces
On Jan 20, 2006, at 1:33 PM, Dain Sundstrom wrote:
This is really a discussion for the openejb mailing list, but since
you asked here I'll respond here.
On Jan 20, 2006, at 11:17 AM, David Jencks wrote:
On Jan 20, 2006, at 9:59 AM, Dain Sundstrom wrote:
On Jan 20, 2006, at 9:46 AM, David
I'd prefer to copy the Geronimo list if the discussion moves. FWIW I think a
lot of folk that are on the G list would be interested. Since OpenEJB is making
the move to Geronimo (assuming it happens) I think it would be good to keep the
thread on this list so the history is cohesive.
Dain Su
Dain Sundstrom wrote:
I have heard from some that 1.1 will be cut next week and from others
that it will be at least 4 more weeks. Can we make a decision now on
what the date will be?
I have a fairly big change I'd like to commit sometime next week, but
if we are going to cut on Friday, I'll
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dain Sundstrom wrote:
>>
>>Who is the release manager? If there isn't one, then there's
>>no point worrying about any particular date. The release
>>manager gets to call the shots on freeze, thaw, and cut dates.
>
> Um, I really disagree here. If t
This is really a discussion for the openejb mailing list, but since
you asked here I'll respond here.
On Jan 20, 2006, at 11:17 AM, David Jencks wrote:
On Jan 20, 2006, at 9:59 AM, Dain Sundstrom wrote:
On Jan 20, 2006, at 9:46 AM, David Jencks wrote:
Personally I am not ready for 1.1 to
On Jan 20, 2006, at 11:42 AM, Rodent of Unusual Size wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dain Sundstrom wrote:
Regardless, of this change, I don't want to be the one that checks in
stuff that breaks the build or TCK 3 days before a branch is cut.
Who is the release manager?
For what it's worth, Dain whiteboarded his plan for me the other day
and I'm 100% on board with the proposed changes.
Thanks,
Aaron
On 1/20/06, David Jencks <[EMAIL PROTECTED]> wrote:
>
> On Jan 20, 2006, at 9:59 AM, Dain Sundstrom wrote:
>
> > On Jan 20, 2006, at 9:46 AM, David Jencks wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dain Sundstrom wrote:
>
> Regardless, of this change, I don't want to be the one that checks in
> stuff that breaks the build or TCK 3 days before a branch is cut.
Who is the release manager? If there isn't one, then there's
no point worrying abou
On Jan 20, 2006, at 9:59 AM, Dain Sundstrom wrote:
On Jan 20, 2006, at 9:46 AM, David Jencks wrote:
Personally I am not ready for 1.1 to be frozen.
Also, there is at least one major bug (tomcat cross-context
dispatch) that needs to be fixed and I haven't seen any progress
on it.
The na
On Jan 20, 2006, at 9:46 AM, David Jencks wrote:
Personally I am not ready for 1.1 to be frozen.
Also, there is at least one major bug (tomcat cross-context
dispatch) that needs to be fixed and I haven't seen any progress on
it.
The nature of your change might affect other peoples opinion
David Jencks wrote:
> Personally I am not ready for 1.1 to be frozen.
>
> Also, there is at least one major bug (tomcat cross-context dispatch)
> that needs to be fixed and I haven't seen any progress on it.
I am not going to be able to get to this at least until Monday...you
know...day job and
Personally I am not ready for 1.1 to be frozen.
Also, there is at least one major bug (tomcat cross-context dispatch)
that needs to be fixed and I haven't seen any progress on it.
The nature of your change might affect other peoples opinion on this
also, what are you planning?
thanks
davi
Nope, I mean 1.1.
-dain
On Jan 20, 2006, at 9:14 AM, Jeff Genender wrote:
Do you mean 1.0.1 for cutting next week?
Dain Sundstrom wrote:
I have heard from some that 1.1 will be cut next week and from others
that it will be at least 4 more weeks. Can we make a decision now on
what the date w
Do you mean 1.0.1 for cutting next week?
Dain Sundstrom wrote:
> I have heard from some that 1.1 will be cut next week and from others
> that it will be at least 4 more weeks. Can we make a decision now on
> what the date will be?
>
> I have a fairly big change I'd like to commit sometime next w
I have heard from some that 1.1 will be cut next week and from others
that it will be at least 4 more weeks. Can we make a decision now on
what the date will be?
I have a fairly big change I'd like to commit sometime next week, but
if we are going to cut on Friday, I'll wait until Saturday
16 matches
Mail list logo
