Re: JDBC 4 Compliance
| От | Dave Cramer |
|---|---|
| Тема | Re: JDBC 4 Compliance |
| Дата | |
| Msg-id | CADK3HHLoUNT1yv2HHE8uyW5=Vhr6jpc6=HPWVi-q6Osijt+sUw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: JDBC 4 Compliance (Bryan Varner <bvarner@polarislabs.com>) |
| Ответы |
Re: JDBC 4 Compliance
(Bryan Varner <bvarner@polarislabs.com>)
Re: JDBC 4 Compliance (Kevin Wooten <kdubb@me.com>) Versioning - was JDBC 4 Compliance (John Lister <john.lister@kickstone.com>) |
| Список | pgsql-jdbc |
On Mon, Jun 24, 2013 at 1:59 PM, Bryan Varner <bvarner@polarislabs.com> wrote:
I'll speak from my own experiences (XA Interleaving) and from watching the mailing list over the last few months. Keep in mind, these are my impressions, which are meant in no way to condemn, vilify, or point the finger at any individual. Rather, I think it points to some cultural pressures on the project as a whole.I would like to start it. I do realize that my lack of time is probably
paramount. But it needs to be solved.
* There are currently six open pull requests [1], some of which date back 10 months. I can understand not merging a pull request. But things this old that aren't merged probably ought to be closed.
Fair enough although 2 of them are yours...
* Initially when we contacted the list about implementing interleaving we got everything from (paraphrased) 'it's a good idea' to 'if you need it then you are doing it wrong'. Everything from our need for it to how we eventually implemented was ridiculed.
* I finally took the time to jump through all the political hoops to clean up the pull request (I still don't understand how a visual diff on github is too hard to follow?!) I created a few months ago into two new pull requests. It's been 3 days, and there's be zero activity or comments on the requests. That seems odd. This is not a minor feature.
Well you posted it on a weekend, so I'd say 1 day really. As I mentioned I do not have the technical ability to comment on it, I need to find someone who does. Let me work on that
* I got the distinct impression that this project consists of an 'old boys club' of developers who've worked on this project for a long time. Outsiders seem to be treated in an almost hostile manner.
Are you referring to the JDBC project or the postgresql project as a whole ?
* A long-standing contributors misplaced emotional attachment to their code should not justify holding on to artifacts which go against logic, reason, and current best practices.
* It seems as though the project is resistant to any form of code-change beyond a trivial bug fix to existing code. This seems like a release management failure more than anything.
I would have to agree large changes are difficult to consume as we don't have the resources to review them, and the project is mainly in maintenance mode.
I completely agree with the assertion that it's easier to fork this project than it is to contribute back to it. I will openly admit that I've considered forking this project personally.
I've only been around since late January / early February, so I hope my perspective in some way helps.
Regards,
-Bryan Varner
[1]: https://github.com/pgjdbc/pgjdbc/pulls
--
Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-jdbc
В списке pgsql-jdbc по дате отправления: