New release schedule?

[Sergey Prokhorov]

I see that epgsql master branch isn't updated since 11 jun 2014 and devel branch has > 60 commits and a lot of improevements. Also, there is incompatible changes (API modules renamed).

Is there any plans to release new version? Some time schedule? Or maybe some critical bugs, which should be fixed before new release can be issued?

For now we have a risk that users may start stick on devel branch in their's rebar.config because of missing features.

[David Welton]

Hi,

Good question.

epgsql is a bit of a stop and go effort for me.

I would like all the tests to pass before we merge everything into
master and bump the major version number. Other than that, I don't
have any timeline or strong feelings about the subject.

The more people are active, the more it brings me back to the project.

--
David N. Welton

http://www.welton.it/davidw/

http://www.dedasys.com/

[David Welton]

Hi,

here's the list of open issues as far as the tests are concerned:

1) Merging the fix_cached_type branch fixes tests in the 'a' and 'i' versions.

2) An ssl error in the tests.

3) A few other random tests that don't pass:
https://groups.google.com/forum/#!topic/epgsql/HEwVr_LSHek

[David Welton]

> 2) An ssl error in the tests.

I have added this to the test schema:

CREATE EXTENSION sslinfo;

I think this is pretty standard these days.

[David Welton]

... and with a few more changes and tweaks, all the tests pass in the
self-contained-pg branch!

Next steps:

* Merge that back into devel. I'm going to do that right now.

* Hopefully people will give it a try and see if everything works for them.

* Merge into master and release.