--
You received this message because you are subscribed to the Google Groups "Erlang epgsql Postgres driver use and development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to epgsql+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/epgsql/64a44188-5d8b-4ead-8320-e90725ae9ae9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi,Now that OTP 22 is out I am for officially dropping 17 support.The list of changes looks good.And if we can’t fix issue 193 (will have a look) then we can alwayspostpone the fix and release a 4.3.1 later.Just mention it in the “known issues”.- Marc
On 21 May 2019, at 23:16, Sergey Prokhorov <ser...@gmail.com> wrote:
Is it time to do next release? Last one was in October 2018. What have changed since then:
* Erlang 22 compatibility is tested; support for Erlang 17 was dropped. Last version that supports Erlang 17 is 4.2.1 (#195)
* Fixed some corner-case bug in streaming replication (#181)
* Performance micro-optimizations on hot paths (#177)
* Use PostgreSQL 10 for Travis tests (#195)
* Improved connection error handling (#183)
* TLS certificates used in tests had expired (epgsql project is more than 10 years old!), so, new ones were created (#187)* Some typespecs fixedWe still have one open bug that was introduced in 4.0 refactoring. It would be really nice to fix before the release, but it's not that strightforward https://github.com/epgsql/epgsql/issues/193--
You received this message because you are subscribed to the Google Groups "Erlang epgsql Postgres driver use and development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to epg...@googlegroups.com.