Re: [JDBC] Cut 42.1.5 now and start merging for 42.2.0? - Mailing list pgsql-jdbc

From Dave Cramer
Subject Re: [JDBC] Cut 42.1.5 now and start merging for 42.2.0?
Date
Msg-id CADK3HHJJvuuMNyoWyNCZEO+YGsi0YQucZYxPcPrTR4wOQcp5dg@mail.gmail.com
Whole thread Raw
In response to [JDBC] Cut 42.1.5 now and start merging for 42.2.0?  (Jorge Solórzano <jorsol@gmail.com>)
Responses Re: [JDBC] Cut 42.1.5 now and start merging for 42.2.0?  (Jorge Solórzano <jorsol@gmail.com>)
List pgsql-jdbc
The idea was to get people to review. How does cutting a version now help us ?




On 4 October 2017 at 13:09, Jorge Solórzano <jorsol@gmail.com> wrote:
The Backlog of pgjdbc is getting bigger and bigger, there are many features that are ready but require review.

Should we cut 42.1.5 now and start merging for 42.2.0? or just start merging ready features and release 42.2.0 soon?

Jorge Solórzano

pgsql-jdbc by date:

Previous
From: Jorge Solórzano
Date:
Subject: [JDBC] Cut 42.1.5 now and start merging for 42.2.0?
Next
From: Jorge Solórzano
Date:
Subject: Re: [JDBC] Cut 42.1.5 now and start merging for 42.2.0?