Re: Cut 42.1.5 now and start merging for 42.2.0?

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: Jorge Solórzano <jorsol(at)gmail(dot)com>
Cc: List <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: Cut 42.1.5 now and start merging for 42.2.0?
Date: 2017-10-05 02:34:57
Message-ID: CADK3HHJJvuuMNyoWyNCZEO+YGsi0YQucZYxPcPrTR4wOQcp5dg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

The idea was to get people to review. How does cutting a version now help
us ?

Dave Cramer

davec(at)postgresintl(dot)com
www.postgresintl.com

On 4 October 2017 at 13:09, Jorge Solórzano <jorsol(at)gmail(dot)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
>

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Jorge Solórzano 2017-10-05 13:39:17 Re: Cut 42.1.5 now and start merging for 42.2.0?
Previous Message Jorge Solórzano 2017-10-04 17:09:57 Cut 42.1.5 now and start merging for 42.2.0?