From: | John Lister <john(dot)lister(at)kickstone(dot)com> |
---|---|
To: | Dave Cramer <pg(at)fastcrypt(dot)com> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: setObject(...) with native Java arrays like String[] ? |
Date: | 2012-08-23 18:09:00 |
Message-ID: | 503671BC.7080204@kickstone.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On 23/08/2012 16:00, Dave Cramer wrote:
> To be candid, I need help managing the patches.
>
> Many times the patches come in without test cases or without
> documentation. All of these things require me to spend time I don't
> have.
>
> Also many patches or requests are very specific "itches" which solve a
> particular problem for the submitter. Every new feature adds
> complexity and possibly negatively effects performance. It is useful
> to keep in mind that the driver is used by lots of other people who
> will not benefit from this particular feature request.
>
>
> So I am open to suggestions as to how to manage this better. I know
> that the main postgresql project has a system where other people
> review patches. This seems like it is a good idea.
>
> Notionally someone other than the submitter would review the patch.
>
Sounds like a good idea, I'm happy to review patches if required. Is
there a set of guidelines that need to be followed
in determining if a patch should be accepted?
John
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2012-08-23 18:16:08 | Re: setObject(...) with native Java arrays like String[] ? |
Previous Message | Dave Cramer | 2012-08-23 15:00:57 | Re: setObject(...) with native Java arrays like String[] ? |