Re: JDBC 4 Compliance

I have indicated I would be willing to help with the web page, but last that
issue came up the use of Apache Forest was considered the default. After
reviewing it I thought it was not conducive to a simple approach to conveying
information. I really mean basic information and providing a mechanism to convey
development work. The keys areas for development it seems to me are todos and
patches? Without these being clearly accurate and accessable to individuals
then no clear goals are communicated.

I would be willing to research as indicated before and alternative to Apache
Forest, but will find a way to use if that remains the default.

---------------------------------------
So may I summarize:

** LACK of RESOURCES:

1. Review Patches (Open)
2. Maven Deployment, Mike Fowler, Build to be still controlled by Dave?
3. Website, Dana Proctor

Kevin Carr in what way would you be willing to contribute, area(s)?

---------------------------------------
** Now I suppose this will generally address the maintenance of the existing
code, But it does not address the issue of pushing the Driver into compliance
with Java 7, 8, etc. and the forks.

This is where I would like to see the website setup for polling, it seems
that the conscious seems to be that there should be:

1. Current pgJDBC to be maintained, but not be pushed forward?
2. Fork(s) to be Version 2 for Java 7, 8 support?

danap.

Mike Fowler wrote:
> Hi Dave,
>
>>
>> Moving forward. As I see it the number one problem is lack of resources.
>> Instead of opting for wholesale change the project needs resources.
>> Someone else to review patches, someone to work on the website. Someone
>> to deploy to maven.
>>
>> Anyone feel like volunteering ?
>>
>
> Let me say a thank you to all the work you have done for the JDBC
> driver. I'm happy to volunteer for both patch review and handling Maven.
> As I already run the JDBC buildfarm
> (www.pgbuildfarm.org/cgi-bin/show_status.pl?member=piapiac) I have a
> stable, repeatable build environment that can be used to make a driver
> release and push it to Maven. I've not done a push to central before but
> I have run a number of CI environments with nexus. I recall there being
> a number of discussions early this year so I'll make a start there.
>
> Kind regards,