You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@commons.apache.org by Phil Steitz <ph...@gmail.com> on 2006/03/08 03:32:11 UTC
[dbcp] Jumping in...
There is a growing backlog of bugs open against [dbcp]. Unless other
committers object, I am going to jump in and start committing patches
and develop a maintenance release plan. I plan to start with
http://issues.apache.org/bugzilla/show_bug.cgi?id=33591
http://issues.apache.org/bugzilla/show_bug.cgi?id=38073
I would appreciate any feedback that community members have on
prioritization of open tickets. Also, as always, tickets with patches
and test cases are likely to get addressed quicker and comments /
testing / feedback are always welcome.
Any help from other commons committers, even if just in the form of
screams, will be most appreciated.
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
Re: [dbcp] Jumping in...
Posted by Rahul Akolkar <ra...@gmail.com>.
On 3/7/06, Phil Steitz <ph...@gmail.com> wrote:
>
> There is a growing backlog of bugs open against [dbcp]. Unless other
> committers object, I am going to jump in and start committing patches
> and develop a maintenance release plan.
>
<snip/>
+1, and thanks.
Fixed some obsolete/broken links on the site, as I was doing a quick
site review .
-Rahul
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [dbcp] Jumping in...
Posted by Henri Yandell <fl...@gmail.com>.
I just use the hugely long:
http://issues.apache.org/bugzilla/report.cgi?x_axis_field=bug_status&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Commons&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=NEEDINFO&bug_severity=blocker&bug_severity=critical&bug_severity=regression&bug_severity=major&bug_severity=normal&bug_severity=minor&bug_severity=trivial&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0=
:)
Did [cli] stuff tonight, but will add [dbcp] to the ones to take a look at.
Hen
On 3/7/06, Phil Steitz <ph...@gmail.com> wrote:
> Thanks!
>
> I added the new commons std issue tracking page here:
> http://jakarta.apache.org/commons/dbcp/issue-tracking.html
>
> One of the links on that page will generate an open bug list. There
> are also instructions for entering new ones (though we are certainly
> not lacking in open tickets ;-)
>
> Anyone wanting to contribute who needs help getting set up with
> ant/maven, svn, generating patches, etc., don't hesitate to ask.
>
> We don't usually use the "voting" feature in Bugzilla, but I am
> willing to try anything once. In any case, weighing in somehow on
> priorities will help us decide which ones to go after first.
>
> Phil
>
> On 3/7/06, Henri Yandell <fl...@gmail.com> wrote:
> > On 3/7/06, Craig McClanahan <cr...@apache.org> wrote:
> > > On 3/7/06, Phil Steitz <ph...@gmail.com> wrote:
> > > >
> > > > There is a growing backlog of bugs open against [dbcp]. Unless other
> > > > committers object, I am going to jump in and start committing patches
> > > > and develop a maintenance release plan.
> > >
> > >
> > > +1 (and thanks) for Phil stepping up to the plate!
> >
> > +1. Let me know how I can help.
> >
> > Hen
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [dbcp] Jumping in...
Posted by Phil Steitz <ph...@gmail.com>.
Thanks!
I added the new commons std issue tracking page here:
http://jakarta.apache.org/commons/dbcp/issue-tracking.html
One of the links on that page will generate an open bug list. There
are also instructions for entering new ones (though we are certainly
not lacking in open tickets ;-)
Anyone wanting to contribute who needs help getting set up with
ant/maven, svn, generating patches, etc., don't hesitate to ask.
We don't usually use the "voting" feature in Bugzilla, but I am
willing to try anything once. In any case, weighing in somehow on
priorities will help us decide which ones to go after first.
Phil
On 3/7/06, Henri Yandell <fl...@gmail.com> wrote:
> On 3/7/06, Craig McClanahan <cr...@apache.org> wrote:
> > On 3/7/06, Phil Steitz <ph...@gmail.com> wrote:
> > >
> > > There is a growing backlog of bugs open against [dbcp]. Unless other
> > > committers object, I am going to jump in and start committing patches
> > > and develop a maintenance release plan.
> >
> >
> > +1 (and thanks) for Phil stepping up to the plate!
>
> +1. Let me know how I can help.
>
> Hen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [dbcp] Jumping in...
Posted by Henri Yandell <fl...@gmail.com>.
On 3/7/06, Craig McClanahan <cr...@apache.org> wrote:
> On 3/7/06, Phil Steitz <ph...@gmail.com> wrote:
> >
> > There is a growing backlog of bugs open against [dbcp]. Unless other
> > committers object, I am going to jump in and start committing patches
> > and develop a maintenance release plan.
>
>
> +1 (and thanks) for Phil stepping up to the plate!
+1. Let me know how I can help.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [dbcp] Jumping in...
Posted by Henri Yandell <fl...@gmail.com>.
On 3/7/06, Craig McClanahan <cr...@apache.org> wrote:
> On 3/7/06, Phil Steitz <ph...@gmail.com> wrote:
> >
> > There is a growing backlog of bugs open against [dbcp]. Unless other
> > committers object, I am going to jump in and start committing patches
> > and develop a maintenance release plan.
>
>
> +1 (and thanks) for Phil stepping up to the plate!
+1. Let me know how I can help.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
Re: [dbcp] Jumping in...
Posted by Craig McClanahan <cr...@apache.org>.
On 3/7/06, Phil Steitz <ph...@gmail.com> wrote:
>
> There is a growing backlog of bugs open against [dbcp]. Unless other
> committers object, I am going to jump in and start committing patches
> and develop a maintenance release plan.
+1 (and thanks) for Phil stepping up to the plate!
Craig
Re: [dbcp] Jumping in...
Posted by Rahul Akolkar <ra...@gmail.com>.
On 3/8/06, robert burrell donkin <ro...@blueyonder.co.uk> wrote:
> On Wed, 2006-03-08 at 21:21 +0100, Jörg Schaible wrote:
<snip/>
> > I can at least apply my patches from Bugzilla, I just did not wanted to
> > start to commit to a project I never committed before ...
>
> +1
>
> we're all one community here: please don't feel constrained to work in
> just one little box.
>
> if you want to work on one of the components here you haven't worked on
> before, just post a hello (as phil did) and then dive in. the worst
> that can happen is a -1 :)
>
<snap/>
+1, the "hello" is needed not because there are hard boundaries, but
rather just so we don't step on each other's feet in our refactorings
within the same branch. For minor changes (broken links on site,
typos, any bugs with localized fixes you have reasonable confidence
in), this isn't an issue, IMO.
-Rahul
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
Re: [dbcp] Jumping in...
Posted by robert burrell donkin <ro...@blueyonder.co.uk>.
On Wed, 2006-03-08 at 21:21 +0100, Jörg Schaible wrote:
> Phil Steitz wrote:
>
> > There is a growing backlog of bugs open against [dbcp]. Unless other
> > committers object, I am going to jump in and start committing patches
> > and develop a maintenance release plan. I plan to start with
> >
> > http://issues.apache.org/bugzilla/show_bug.cgi?id=33591
> > http://issues.apache.org/bugzilla/show_bug.cgi?id=38073
> >
> > I would appreciate any feedback that community members have on
> > prioritization of open tickets. Also, as always, tickets with patches
> > and test cases are likely to get addressed quicker and comments /
> > testing / feedback are always welcome.
> >
> > Any help from other commons committers, even if just in the form of
> > screams, will be most appreciated.
>
> I can at least apply my patches from Bugzilla, I just did not wanted to
> start to commit to a project I never committed before ...
+1
we're all one community here: please don't feel constrained to work in
just one little box.
if you want to work on one of the components here you haven't worked on
before, just post a hello (as phil did) and then dive in. the worst
that can happen is a -1 :)
remember to add yourself to the list of committers for that component.
if you're embarking on a major rewrite (rather than just bug fixes),
consider either starting work on a branch or taking a tag.
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
Re: [dbcp] Jumping in...
Posted by Jörg Schaible <jo...@gmx.de>.
Jörg Schaible wrote:
> Phil Steitz wrote:
>
>> There is a growing backlog of bugs open against [dbcp]. Unless other
>> committers object, I am going to jump in and start committing patches
>> and develop a maintenance release plan. I plan to start with
>>
>> http://issues.apache.org/bugzilla/show_bug.cgi?id=33591
>> http://issues.apache.org/bugzilla/show_bug.cgi?id=38073
>>
>> I would appreciate any feedback that community members have on
>> prioritization of open tickets. Also, as always, tickets with patches
>> and test cases are likely to get addressed quicker and comments /
>> testing / feedback are always welcome.
>>
>> Any help from other commons committers, even if just in the form of
>> screams, will be most appreciated.
>
> I can at least apply my patches from Bugzilla, I just did not wanted to
> start to commit to a project I never committed before ...
http://issues.apache.org/bugzilla/show_bug.cgi?id=36685
Done. Nice: Eclipse 3.2M5 has a new feature to detect such situations, so I
could fix a lot more possible NPE situations in finally blocks.
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
Re: [dbcp] Jumping in...
Posted by robert burrell donkin <ro...@blueyonder.co.uk>.
On Wed, 2006-03-08 at 21:21 +0100, Jörg Schaible wrote:
> Phil Steitz wrote:
>
> > There is a growing backlog of bugs open against [dbcp]. Unless other
> > committers object, I am going to jump in and start committing patches
> > and develop a maintenance release plan. I plan to start with
> >
> > http://issues.apache.org/bugzilla/show_bug.cgi?id=33591
> > http://issues.apache.org/bugzilla/show_bug.cgi?id=38073
> >
> > I would appreciate any feedback that community members have on
> > prioritization of open tickets. Also, as always, tickets with patches
> > and test cases are likely to get addressed quicker and comments /
> > testing / feedback are always welcome.
> >
> > Any help from other commons committers, even if just in the form of
> > screams, will be most appreciated.
>
> I can at least apply my patches from Bugzilla, I just did not wanted to
> start to commit to a project I never committed before ...
+1
we're all one community here: please don't feel constrained to work in
just one little box.
if you want to work on one of the components here you haven't worked on
before, just post a hello (as phil did) and then dive in. the worst
that can happen is a -1 :)
remember to add yourself to the list of committers for that component.
if you're embarking on a major rewrite (rather than just bug fixes),
consider either starting work on a branch or taking a tag.
- robert
Re: [dbcp] Jumping in...
Posted by Jörg Schaible <jo...@gmx.de>.
Phil Steitz wrote:
> There is a growing backlog of bugs open against [dbcp]. Unless other
> committers object, I am going to jump in and start committing patches
> and develop a maintenance release plan. I plan to start with
>
> http://issues.apache.org/bugzilla/show_bug.cgi?id=33591
> http://issues.apache.org/bugzilla/show_bug.cgi?id=38073
>
> I would appreciate any feedback that community members have on
> prioritization of open tickets. Also, as always, tickets with patches
> and test cases are likely to get addressed quicker and comments /
> testing / feedback are always welcome.
>
> Any help from other commons committers, even if just in the form of
> screams, will be most appreciated.
I can at least apply my patches from Bugzilla, I just did not wanted to
start to commit to a project I never committed before ...
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
Re: [dbcp] Jumping in...
Posted by James Ring <sj...@jdns.org>.
Hi Phil,
On Wednesday 08 March 2006 14:07, Phil Steitz wrote:
> Thanks in advance for your help. On 33591 specifically, any comments
> that you have on which of the solutions in the ticket is cleanest /
> safest would be appreciated. I am testing your patch now, but am also
> evaluating Dirk's. A test case showing the leak (i.e. fails with
> current code) would also be great.
Ok, if nobody else submits one before tonight (12 hours or so), I'll try and
come up with a test case.
I wish my day job would pay me to work on Commons. ;-)
> Phil
Thanks for your time.
Regards,
James
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [dbcp] Jumping in...
Posted by Phil Steitz <ph...@gmail.com>.
On 3/7/06, James Ring <sj...@jdns.org> wrote:
> Hi Phil,
>
> On Wednesday 08 March 2006 13:32, Phil Steitz wrote:
> > There is a growing backlog of bugs open against [dbcp]. Unless other
> > committers object, I am going to jump in and start committing patches
> > and develop a maintenance release plan. I plan to start with
> >
> > http://issues.apache.org/bugzilla/show_bug.cgi?id=33591
> > http://issues.apache.org/bugzilla/show_bug.cgi?id=38073
>
> Here here!
>
> I'm not a committer, but I would really like to see some of this backlog
> cleared. Especially with regards to 33591, which has had a fix available for
> a while and which is quite a nasty one.
Thanks in advance for your help. On 33591 specifically, any comments
that you have on which of the solutions in the ticket is cleanest /
safest would be appreciated. I am testing your patch now, but am also
evaluating Dirk's. A test case showing the leak (i.e. fails with
current code) would also be great.
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [dbcp] Jumping in...
Posted by James Ring <sj...@jdns.org>.
Hi Phil,
On Wednesday 08 March 2006 13:32, Phil Steitz wrote:
> There is a growing backlog of bugs open against [dbcp]. Unless other
> committers object, I am going to jump in and start committing patches
> and develop a maintenance release plan. I plan to start with
>
> http://issues.apache.org/bugzilla/show_bug.cgi?id=33591
> http://issues.apache.org/bugzilla/show_bug.cgi?id=38073
Here here!
I'm not a committer, but I would really like to see some of this backlog
cleared. Especially with regards to 33591, which has had a fix available for
a while and which is quite a nasty one.
> I would appreciate any feedback that community members have on
> prioritization of open tickets. Also, as always, tickets with patches
> and test cases are likely to get addressed quicker and comments /
> testing / feedback are always welcome.
>
> Any help from other commons committers, even if just in the form of
> screams, will be most appreciated.
There haven't been any code changes in over twelve months. It would be nice to
fix the outstanding issues and then push out a bugfix release.
> Phil
Thanks,
James
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [dbcp] Jumping in...
Posted by Craig McClanahan <cr...@apache.org>.
On 3/7/06, Phil Steitz <ph...@gmail.com> wrote:
>
> There is a growing backlog of bugs open against [dbcp]. Unless other
> committers object, I am going to jump in and start committing patches
> and develop a maintenance release plan.
+1 (and thanks) for Phil stepping up to the plate!
Craig
Re: [dbcp] Jumping in...
Posted by Sandy McArthur <sa...@apache.org>.
I'm not familar with the dbcp codebase yet but near the release of
Pool 2.0 it is my intention to get familar with it and make sure it
works well with the semantic changes. Maybe also switch dbcp to the
composite pool impl if that is acceptable to everyone. In the mean go
for it.
On 3/7/06, Phil Steitz <ph...@gmail.com> wrote:
> There is a growing backlog of bugs open against [dbcp]. Unless other
> committers object, I am going to jump in and start committing patches
> and develop a maintenance release plan. I plan to start with
>
> http://issues.apache.org/bugzilla/show_bug.cgi?id=33591
> http://issues.apache.org/bugzilla/show_bug.cgi?id=38073
>
> I would appreciate any feedback that community members have on
> prioritization of open tickets. Also, as always, tickets with patches
> and test cases are likely to get addressed quicker and comments /
> testing / feedback are always welcome.
>
> Any help from other commons committers, even if just in the form of
> screams, will be most appreciated.
>
> Phil
--
Sandy McArthur
"He who dares not offend cannot be honest."
- Thomas Paine
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org
Re: [dbcp] Jumping in...
Posted by Sandy McArthur <sa...@apache.org>.
I'm not familar with the dbcp codebase yet but near the release of
Pool 2.0 it is my intention to get familar with it and make sure it
works well with the semantic changes. Maybe also switch dbcp to the
composite pool impl if that is acceptable to everyone. In the mean go
for it.
On 3/7/06, Phil Steitz <ph...@gmail.com> wrote:
> There is a growing backlog of bugs open against [dbcp]. Unless other
> committers object, I am going to jump in and start committing patches
> and develop a maintenance release plan. I plan to start with
>
> http://issues.apache.org/bugzilla/show_bug.cgi?id=33591
> http://issues.apache.org/bugzilla/show_bug.cgi?id=38073
>
> I would appreciate any feedback that community members have on
> prioritization of open tickets. Also, as always, tickets with patches
> and test cases are likely to get addressed quicker and comments /
> testing / feedback are always welcome.
>
> Any help from other commons committers, even if just in the form of
> screams, will be most appreciated.
>
> Phil
--
Sandy McArthur
"He who dares not offend cannot be honest."
- Thomas Paine
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org