Обсуждение: [JDBC] Beta/RC release?
PgJDBC is close to a major 42 release, but should be released first a Beta/RC to get feedback and catch potential issues first? It's just a question to know opinions.
Jorge Solórzano
On 13 February 2017 at 10:56, Jorge Solórzano <jorsol@gmail.com> wrote:
PgJDBC is close to a major 42 release, but should be released first a Beta/RC to get feedback and catch potential issues first? It's just a question to know opinions.
We just release it. Historically nobody provides any feedback
On 13 February 2017 at 10:56, Jorge Solórzano <jorsol@gmail.com> wrote:
PgJDBC is close to a major 42 release, but should be released first a Beta/RC to get feedback and catch potential issues first? It's just a question to know opinions.
We just release it. Historically nobody provides any feedback
Just in case: I've pushed 42.0.0 artifacts to Maven Central (see [1], [2], [3])
The release could be announced as Dave updates the site.
In the mean time, feel free to test artifacts and/or review release notes:
Vladimir
пн, 13 февр. 2017 г. в 19:14, Dave Cramer <pg@fastcrypt.com>:
On 13 February 2017 at 10:56, Jorge Solórzano <jorsol@gmail.com> wrote:PgJDBC is close to a major 42 release, but should be released first a Beta/RC to get feedback and catch potential issues first? It's just a question to know opinions.We just release it. Historically nobody provides any feedback
Just in case: I've pushed 42.0.0 artifacts to Maven Central (see [1], [2], [3])
The release could be announced as Dave updates the site.
In the mean time, feel free to test artifacts and/or review release notes:
Vladimir
пн, 13 февр. 2017 г. в 19:14, Dave Cramer <pg@fastcrypt.com>:
On 13 February 2017 at 10:56, Jorge Solórzano <jorsol@gmail.com> wrote:PgJDBC is close to a major 42 release, but should be released first a Beta/RC to get feedback and catch potential issues first? It's just a question to know opinions.We just release it. Historically nobody provides any feedback
On 02/18/2017 02:17 PM, Vladimir Sitnikov wrote: > https://github.com/pgjdbc/pgjdbc/blob/master/docs/documentation/_changelog/42.0.0-notes.md The links "logging documentation" and "replication API documentation" return 404s. -- Glenn Holmer (Linux registered user #16682) "After the vintage season came the aftermath -- and Cenbe."
On 02/18/2017 02:17 PM, Vladimir Sitnikov wrote: > https://github.com/pgjdbc/pgjdbc/blob/master/docs/documentation/_changelog/42.0.0-notes.md The links "logging documentation" and "replication API documentation" return 404s. -- Glenn Holmer (Linux registered user #16682) "After the vintage season came the aftermath -- and Cenbe."
I need to update the main site then they won't 404. Working on it.
On 19 February 2017 at 11:19, Glenn Holmer <cenbe@kolabnow.com> wrote:
On 02/18/2017 02:17 PM, Vladimir Sitnikov wrote:
> https://github.com/pgjdbc/pgjdbc/blob/master/docs/ documentation/_changelog/42.0. 0-notes.md
The links "logging documentation" and "replication API documentation"
return 404s.
--
Glenn Holmer (Linux registered user #16682)
"After the vintage season came the aftermath -- and Cenbe."
--
Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-jdbc
I need to update the main site then they won't 404. Working on it.
On 19 February 2017 at 11:19, Glenn Holmer <cenbe@kolabnow.com> wrote:
On 02/18/2017 02:17 PM, Vladimir Sitnikov wrote:
> https://github.com/pgjdbc/pgjdbc/blob/master/docs/ documentation/_changelog/42.0. 0-notes.md
The links "logging documentation" and "replication API documentation"
return 404s.
--
Glenn Holmer (Linux registered user #16682)
"After the vintage season came the aftermath -- and Cenbe."
--
Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-jdbc