Release 2.1?

81 views
Skip to first unread message

Shay Rojansky

unread,
Mar 4, 2014, 12:10:01 PM3/4/14
to npgsq...@googlegroups.com
What do you guys think? It's been 3 weeks since the RC release...

Francisco Figueiredo Jr.

unread,
Mar 4, 2014, 6:54:36 PM3/4/14
to Shay Rojansky, npgsq...@googlegroups.com

Although the tag has been done 3 weeks ago, the official release only happened last week.

I agree with you and I think we should create a final release for 2.1. In fact when  I created the blog post about the rc1 I said we would make the final release in the first days of March.

I remember we received a report about problems using EF with ssl. I'll check that.



Em 04/03/2014 14:10, "Shay Rojansky" <ro...@roji.org> escreveu:
What do you guys think? It's been 3 weeks since the RC release...

--
You received this message because you are subscribed to the Google Groups "Npgsql Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to npgsql-dev+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Francisco Figueiredo Jr.

unread,
Mar 9, 2014, 1:22:03 PM3/9/14
to Shay Rojansky, npgsq...@googlegroups.com
Hi, all!

I figure the SSL problem. It isn't related only to EF. In fact, SSL
connections currently are broken. :(

According to this issue: https://github.com/npgsql/Npgsql/issues/176
the problem lies in the fact that the new code for SSLStream support
is missing a check and then it is trying to use the new SSL code
regardless of settings to use it or not. The requirement to use the
new code was the existence of a validator of remote certificate. The
problem is that the patch adds a default validator which returns false
to all remote certificates and thus doesn't allow the ssl handshake to
proceed.

The initial workaround is to provide another validator which returns
true to this validation but even so, the problem isn't completely
solved because with current Npgsql code, Mono ssl can't be used.

I already asked @dreamlax (who created the patch) to have a look at it
but he didn't return back yet. I'll see how I can get it working and
will post back here. My first thought is to change the default remote
certificate validation to return true which makes the code works
without any user intervention.
--
Regards,

Francisco Figueiredo Jr.
Npgsql Lead Developer
http://www.npgsql.org
http://gplus.to/franciscojunior
http://fxjr.blogspot.com
http://twitter.com/franciscojunior

Francisco Figueiredo Jr.

unread,
Mar 9, 2014, 1:33:09 PM3/9/14
to Shay Rojansky, npgsq...@googlegroups.com
Regarding the 2.1. final, I'd like to propose to apply the following patches:

https://github.com/npgsql/Npgsql/pull/174 - GetResultSchema When
current description is null

https://github.com/npgsql/Npgsql/pull/164 - Connection state throws
error incorrectly

What do you all think?

Francisco Figueiredo Jr.

unread,
Mar 13, 2014, 5:44:19 PM3/13/14
to Shay Rojansky, npgsq...@googlegroups.com

Hi all!

I think we are ready to create the final release of 2.1. What do you think?

Glen Parker

unread,
Mar 14, 2014, 12:20:02 AM3/14/14
to Francisco Figueiredo Jr., Shay Rojansky, npgsq...@googlegroups.com
I agree.  RC1 has produced no negative feedback that I'm aware of, and 2.1 doesn't have the (nasty) transaction rollback timeout bug, so there's really nothing standing in the way.

I should be able to do the Nuget this weekend, if we're all on board.

-Glen



For more options, visit https://groups.google.com/d/optout.

Francisco Figueiredo Jr.

unread,
Mar 14, 2014, 12:41:37 PM3/14/14
to Glen Parker, Shay Rojansky, npgsq...@googlegroups.com
On Fri, Mar 14, 2014 at 1:20 AM, Glen Parker <glen...@gmail.com> wrote:
I agree.  RC1 has produced no negative feedback that I'm aware of, and 2.1 doesn't have the (nasty) transaction rollback timeout bug, so there's really nothing standing in the way.


Great! I also fixed a bug in the SSL setup which was preventing Npgsql to work with SSL connections. 
 

I should be able to do the Nuget this weekend, if we're all on board.


I'm on board. I'll create the announcement email and will update the Npgsql homepage. 

We also need to change the assembly version in 2.1 branch to remove the rc string. I'll take care of that.

Francisco Figueiredo Jr.

unread,
Mar 14, 2014, 1:12:18 PM3/14/14
to Glen Parker, Shay Rojansky, npgsq...@googlegroups.com
On Fri, Mar 14, 2014 at 1:41 PM, Francisco Figueiredo Jr. <fran...@npgsql.org> wrote:



On Fri, Mar 14, 2014 at 1:20 AM, Glen Parker <glen...@gmail.com> wrote:
I agree.  RC1 has produced no negative feedback that I'm aware of, and 2.1 doesn't have the (nasty) transaction rollback timeout bug, so there's really nothing standing in the way.


Great! I also fixed a bug in the SSL setup which was preventing Npgsql to work with SSL connections. 
 

I should be able to do the Nuget this weekend, if we're all on board.


I'm on board. I'll create the announcement email and will update the Npgsql homepage. 

We also need to change the assembly version in 2.1 branch to remove the rc string. I'll take care of that.


Francisco Figueiredo Jr.

unread,
Mar 17, 2014, 3:57:02 PM3/17/14
to Glen Parker, Shay Rojansky, npgsq...@googlegroups.com

Hi all!

I already created the release mail and the release notes on github (in draft mode. ready to be released).

Glen, did you upload the packages to nuget? If you didn't, I can upload them.

I think we are almost ready to make the 2.1 final release. :)

Francisco Figueiredo Jr.

unread,
Mar 19, 2014, 5:04:42 PM3/19/14
to Glen Parker, Shay Rojansky, npgsq...@googlegroups.com

Hi, all!

Npgsql 2.1.0 is released!

I still need to upload the files to pgfoundry. I'll be doing this soon.





Christian LeMoussel

unread,
Mar 20, 2014, 4:18:41 AM3/20/14
to npgsq...@googlegroups.com, Glen Parker, Shay Rojansky, fran...@npgsql.org
Very good news ;)

Thank you.
Reply all
Reply to author
Forward
0 new messages