Re: Fw: Fixing bugs in Struts code moved to Commons

["Craig R. McClanahan" <cr...@apache.org>]

Sorry for the slow response -- commitments on Tomcat yadda yadda (Tomcat
4.0 final will be in a couple of weeks :-).

Such issues really need to be addressed in both developments -- in the
Struts copy of these classes for a 1.0.1 release, and here for the
corresponding commons versions used in Struts 1.1.

I will commit the changes (in both places) for this one tomorrow.

Craig


On Tue, 4 Sep 2001 martin.cooper@tumbleweed.com wrote:

> Date: Tue, 4 Sep 2001 21:04:40 -0700
> From: martin.cooper@tumbleweed.com
> Reply-To: jakarta-commons@jakarta.apache.org
> To: jakarta-commons@jakarta.apache.org
> Subject: Fw: Fixing bugs in Struts code moved to Commons
>
> I posted this to struts-dev a week ago and received no response, so I
> figured it's time to see what the folks over here in jakarta-commons think.
> :-)
>
> --
> Martin Cooper
>
>
> ----- Original Message -----
> From: <ma...@tumbleweed.com>
> To: <st...@jakarta.apache.org>
> Sent: Tuesday, August 28, 2001 8:59 PM
> Subject: Fixing bugs in Struts code moved to Commons
>
>
> > There is at least one bug (#2494) in the Struts bug database which is in
> > code moved to Commons after the Struts 1.0 release. To be fixed properly,
> > the change should be made both in the Struts code base (for Struts 1.0.1)
> > and in the Commons code base.
> >
> > How should we manage this type of issue? I assume not all Struts
> committers
> > are also Commons committers (I don't think I am), so I can think of a
> couple
> > of options:
> >
> > 1) Fix the Struts bug and enter a new bug report against the Commons code.
> > 2) Have only committers on both projects address these bugs.
> >
> > I can see pros and cons to both options.
> >
> > Thoughts?
> >
> > --
> > Martin Cooper
> >
> >
> >
>
>
>

Re: Fw: Fixing bugs in Struts code moved to Commons

[Ted Husted <hu...@apache.org>]

I don't think it would be a problem to make you a Commons committer too.
I'm one, and so is Craig and Vincent, and perhaps others. If you want to
help maintain the codebase, no one's going to want to stop you ;-)

I haven't been active in the Commons since it was founded, but would
quickly toss you a +1 if someone brings you up for a vote.

Of course, the dual maintenance issues will eventually pass, as we start
more packages in the Commons to begin with, as is being done with the
workflow. 

martin.cooper@tumbleweed.com wrote:
> 
> ----- Original Message -----
> From: "Craig R. McClanahan" <cr...@apache.org>
> To: <ja...@jakarta.apache.org>
> Cc: <st...@jakarta.apache.org>
> Sent: Tuesday, September 04, 2001 10:06 PM
> Subject: Re: Fw: Fixing bugs in Struts code moved to Commons
> 
> > Sorry for the slow response -- commitments on Tomcat yadda yadda (Tomcat
> > 4.0 final will be in a couple of weeks :-).
> 
> No problem - I know that tune rather well myself...
> 
> > Such issues really need to be addressed in both developments -- in the
> > Struts copy of these classes for a 1.0.1 release, and here for the
> > corresponding commons versions used in Struts 1.1.
> 
> Yes, that was the gist of my message. Do you have any thoughts on the best
> way to manage this type of issue going forward? I'm happy to make fixes to
> Struts, but I'd want to make sure that appropriate changes are (or will be)
> made in Commons where appropriate.
> 
> > I will commit the changes (in both places) for this one tomorrow.
> 
> That would be great - thanks!
> 
> --
> Martin Cooper
> 
> > Craig
> >
> >
> > On Tue, 4 Sep 2001 martin.cooper@tumbleweed.com wrote:
> >
> > > Date: Tue, 4 Sep 2001 21:04:40 -0700
> > > From: martin.cooper@tumbleweed.com
> > > Reply-To: jakarta-commons@jakarta.apache.org
> > > To: jakarta-commons@jakarta.apache.org
> > > Subject: Fw: Fixing bugs in Struts code moved to Commons
> > >
> > > I posted this to struts-dev a week ago and received no response, so I
> > > figured it's time to see what the folks over here in jakarta-commons
> think.
> > > :-)
> > >
> > > --
> > > Martin Cooper
> > >
> > >
> > > ----- Original Message -----
> > > From: <ma...@tumbleweed.com>
> > > To: <st...@jakarta.apache.org>
> > > Sent: Tuesday, August 28, 2001 8:59 PM
> > > Subject: Fixing bugs in Struts code moved to Commons
> > >
> > >
> > > > There is at least one bug (#2494) in the Struts bug database which is
> in
> > > > code moved to Commons after the Struts 1.0 release. To be fixed
> properly,
> > > > the change should be made both in the Struts code base (for Struts
> 1.0.1)
> > > > and in the Commons code base.
> > > >
> > > > How should we manage this type of issue? I assume not all Struts
> > > committers
> > > > are also Commons committers (I don't think I am), so I can think of a
> > > couple
> > > > of options:
> > > >
> > > > 1) Fix the Struts bug and enter a new bug report against the Commons
> code.
> > > > 2) Have only committers on both projects address these bugs.
> > > >
> > > > I can see pros and cons to both options.
> > > >
> > > > Thoughts?
> > > >
> > > > --
> > > > Martin Cooper

Re: Fw: Fixing bugs in Struts code moved to Commons

[ma...@tumbleweed.com]

Sure, that would be fine with me. Thanks!

--
Martin Cooper


----- Original Message -----
From: "Craig R. McClanahan" <cr...@apache.org>
To: <st...@jakarta.apache.org>
Cc: <ja...@jakarta.apache.org>
Sent: Wednesday, September 05, 2001 8:34 AM
Subject: Re: Fw: Fixing bugs in Struts code moved to Commons


> The simplest thing might be to propose you as a committer in Commons as
> well -- that way, there would be two sets of eyes watching for things that
> need to be posted both places.  Sound good?
>
> Craig
>
>
>
> On Tue, 4 Sep 2001 martin.cooper@tumbleweed.com wrote:
>
> > Date: Tue, 4 Sep 2001 22:47:39 -0700
> > From: martin.cooper@tumbleweed.com
> > Reply-To: struts-dev@jakarta.apache.org
> > To: jakarta-commons@jakarta.apache.org
> > Cc: struts-dev@jakarta.apache.org
> > Subject: Re: Fw: Fixing bugs in Struts code moved to Commons
> >
> >
> > ----- Original Message -----
> > From: "Craig R. McClanahan" <cr...@apache.org>
> > To: <ja...@jakarta.apache.org>
> > Cc: <st...@jakarta.apache.org>
> > Sent: Tuesday, September 04, 2001 10:06 PM
> > Subject: Re: Fw: Fixing bugs in Struts code moved to Commons
> >
> >
> > > Sorry for the slow response -- commitments on Tomcat yadda yadda
(Tomcat
> > > 4.0 final will be in a couple of weeks :-).
> >
> > No problem - I know that tune rather well myself...
> >
> > > Such issues really need to be addressed in both developments -- in the
> > > Struts copy of these classes for a 1.0.1 release, and here for the
> > > corresponding commons versions used in Struts 1.1.
> >
> > Yes, that was the gist of my message. Do you have any thoughts on the
best
> > way to manage this type of issue going forward? I'm happy to make fixes
to
> > Struts, but I'd want to make sure that appropriate changes are (or will
be)
> > made in Commons where appropriate.
> >
> > > I will commit the changes (in both places) for this one tomorrow.
> >
> > That would be great - thanks!
> >
> > --
> > Martin Cooper
> >
> > > Craig
> > >
> > >
> > > On Tue, 4 Sep 2001 martin.cooper@tumbleweed.com wrote:
> > >
> > > > Date: Tue, 4 Sep 2001 21:04:40 -0700
> > > > From: martin.cooper@tumbleweed.com
> > > > Reply-To: jakarta-commons@jakarta.apache.org
> > > > To: jakarta-commons@jakarta.apache.org
> > > > Subject: Fw: Fixing bugs in Struts code moved to Commons
> > > >
> > > > I posted this to struts-dev a week ago and received no response, so
I
> > > > figured it's time to see what the folks over here in jakarta-commons
> > think.
> > > > :-)
> > > >
> > > > --
> > > > Martin Cooper
> > > >
> > > >
> > > > ----- Original Message -----
> > > > From: <ma...@tumbleweed.com>
> > > > To: <st...@jakarta.apache.org>
> > > > Sent: Tuesday, August 28, 2001 8:59 PM
> > > > Subject: Fixing bugs in Struts code moved to Commons
> > > >
> > > >
> > > > > There is at least one bug (#2494) in the Struts bug database which
is
> > in
> > > > > code moved to Commons after the Struts 1.0 release. To be fixed
> > properly,
> > > > > the change should be made both in the Struts code base (for Struts
> > 1.0.1)
> > > > > and in the Commons code base.
> > > > >
> > > > > How should we manage this type of issue? I assume not all Struts
> > > > committers
> > > > > are also Commons committers (I don't think I am), so I can think
of a
> > > > couple
> > > > > of options:
> > > > >
> > > > > 1) Fix the Struts bug and enter a new bug report against the
Commons
> > code.
> > > > > 2) Have only committers on both projects address these bugs.
> > > > >
> > > > > I can see pros and cons to both options.
> > > > >
> > > > > Thoughts?
> > > > >
> > > > > --
> > > > > Martin Cooper
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > >
> >
> >
> >
>

Re: Fw: Fixing bugs in Struts code moved to Commons

["Craig R. McClanahan" <cr...@apache.org>]

The simplest thing might be to propose you as a committer in Commons as
well -- that way, there would be two sets of eyes watching for things that
need to be posted both places.  Sound good?

Craig



On Tue, 4 Sep 2001 martin.cooper@tumbleweed.com wrote:

> Date: Tue, 4 Sep 2001 22:47:39 -0700
> From: martin.cooper@tumbleweed.com
> Reply-To: struts-dev@jakarta.apache.org
> To: jakarta-commons@jakarta.apache.org
> Cc: struts-dev@jakarta.apache.org
> Subject: Re: Fw: Fixing bugs in Struts code moved to Commons
>
>
> ----- Original Message -----
> From: "Craig R. McClanahan" <cr...@apache.org>
> To: <ja...@jakarta.apache.org>
> Cc: <st...@jakarta.apache.org>
> Sent: Tuesday, September 04, 2001 10:06 PM
> Subject: Re: Fw: Fixing bugs in Struts code moved to Commons
>
>
> > Sorry for the slow response -- commitments on Tomcat yadda yadda (Tomcat
> > 4.0 final will be in a couple of weeks :-).
>
> No problem - I know that tune rather well myself...
>
> > Such issues really need to be addressed in both developments -- in the
> > Struts copy of these classes for a 1.0.1 release, and here for the
> > corresponding commons versions used in Struts 1.1.
>
> Yes, that was the gist of my message. Do you have any thoughts on the best
> way to manage this type of issue going forward? I'm happy to make fixes to
> Struts, but I'd want to make sure that appropriate changes are (or will be)
> made in Commons where appropriate.
>
> > I will commit the changes (in both places) for this one tomorrow.
>
> That would be great - thanks!
>
> --
> Martin Cooper
>
> > Craig
> >
> >
> > On Tue, 4 Sep 2001 martin.cooper@tumbleweed.com wrote:
> >
> > > Date: Tue, 4 Sep 2001 21:04:40 -0700
> > > From: martin.cooper@tumbleweed.com
> > > Reply-To: jakarta-commons@jakarta.apache.org
> > > To: jakarta-commons@jakarta.apache.org
> > > Subject: Fw: Fixing bugs in Struts code moved to Commons
> > >
> > > I posted this to struts-dev a week ago and received no response, so I
> > > figured it's time to see what the folks over here in jakarta-commons
> think.
> > > :-)
> > >
> > > --
> > > Martin Cooper
> > >
> > >
> > > ----- Original Message -----
> > > From: <ma...@tumbleweed.com>
> > > To: <st...@jakarta.apache.org>
> > > Sent: Tuesday, August 28, 2001 8:59 PM
> > > Subject: Fixing bugs in Struts code moved to Commons
> > >
> > >
> > > > There is at least one bug (#2494) in the Struts bug database which is
> in
> > > > code moved to Commons after the Struts 1.0 release. To be fixed
> properly,
> > > > the change should be made both in the Struts code base (for Struts
> 1.0.1)
> > > > and in the Commons code base.
> > > >
> > > > How should we manage this type of issue? I assume not all Struts
> > > committers
> > > > are also Commons committers (I don't think I am), so I can think of a
> > > couple
> > > > of options:
> > > >
> > > > 1) Fix the Struts bug and enter a new bug report against the Commons
> code.
> > > > 2) Have only committers on both projects address these bugs.
> > > >
> > > > I can see pros and cons to both options.
> > > >
> > > > Thoughts?
> > > >
> > > > --
> > > > Martin Cooper
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
>
>
>

Re: Fw: Fixing bugs in Struts code moved to Commons

[ma...@tumbleweed.com]

----- Original Message -----
From: "Craig R. McClanahan" <cr...@apache.org>
To: <ja...@jakarta.apache.org>
Cc: <st...@jakarta.apache.org>
Sent: Tuesday, September 04, 2001 10:06 PM
Subject: Re: Fw: Fixing bugs in Struts code moved to Commons


> Sorry for the slow response -- commitments on Tomcat yadda yadda (Tomcat
> 4.0 final will be in a couple of weeks :-).

No problem - I know that tune rather well myself...

> Such issues really need to be addressed in both developments -- in the
> Struts copy of these classes for a 1.0.1 release, and here for the
> corresponding commons versions used in Struts 1.1.

Yes, that was the gist of my message. Do you have any thoughts on the best
way to manage this type of issue going forward? I'm happy to make fixes to
Struts, but I'd want to make sure that appropriate changes are (or will be)
made in Commons where appropriate.

> I will commit the changes (in both places) for this one tomorrow.

That would be great - thanks!

--
Martin Cooper

> Craig
>
>
> On Tue, 4 Sep 2001 martin.cooper@tumbleweed.com wrote:
>
> > Date: Tue, 4 Sep 2001 21:04:40 -0700
> > From: martin.cooper@tumbleweed.com
> > Reply-To: jakarta-commons@jakarta.apache.org
> > To: jakarta-commons@jakarta.apache.org
> > Subject: Fw: Fixing bugs in Struts code moved to Commons
> >
> > I posted this to struts-dev a week ago and received no response, so I
> > figured it's time to see what the folks over here in jakarta-commons
think.
> > :-)
> >
> > --
> > Martin Cooper
> >
> >
> > ----- Original Message -----
> > From: <ma...@tumbleweed.com>
> > To: <st...@jakarta.apache.org>
> > Sent: Tuesday, August 28, 2001 8:59 PM
> > Subject: Fixing bugs in Struts code moved to Commons
> >
> >
> > > There is at least one bug (#2494) in the Struts bug database which is
in
> > > code moved to Commons after the Struts 1.0 release. To be fixed
properly,
> > > the change should be made both in the Struts code base (for Struts
1.0.1)
> > > and in the Commons code base.
> > >
> > > How should we manage this type of issue? I assume not all Struts
> > committers
> > > are also Commons committers (I don't think I am), so I can think of a
> > couple
> > > of options:
> > >
> > > 1) Fix the Struts bug and enter a new bug report against the Commons
code.
> > > 2) Have only committers on both projects address these bugs.
> > >
> > > I can see pros and cons to both options.
> > >
> > > Thoughts?
> > >
> > > --
> > > Martin Cooper
> > >
> > >
> > >
> >
> >
> >
>