A release with the boolean fix? about npgsql HOT 11 CLOSED

@ringods, can you please add a unit test for this fix? Or at the very least post a repro here?

from npgsql.

@roji I'm the release manager in a company using .NET. I'm not a .NET developer myself. The developer who patched our version has tested this manually. I doubt I can get hist manager so far as to let him work on this again. Sorry!

from npgsql.

OK, thanks @ringods. I'll try to look at this myself.

Thanks for contributing the fix.

from npgsql.

FYI, my company didn't provide the fix. We just matched our internal fix with the mentioned commit. :-)

from npgsql.

Oh OK, didn't read closely enough :) Thanks for commenting in any case.

from npgsql.

Hi guys,

If there's no objection, I'll bring the bool fix into the 2.0.12 branch,
update for 2.0.14.3, and put a new nuget package out tomorrow.

-Glen

On Fri, Dec 20, 2013 at 8:50 AM, Shay Rojansky [email protected]:

Oh OK, didn't read closely enough :) Thanks for commenting in any case.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/132#issuecomment-31023527
.

from npgsql.

+1

Excellent, Glen!
Em 20/12/2013 16:02, "Glen Parker" [email protected] escreveu:

Hi guys,

If there's no objection, I'll bring the bool fix into the 2.0.12 branch,
update for 2.0.14.3, and put a new nuget package out tomorrow.

-Glen

On Fri, Dec 20, 2013 at 8:50 AM, Shay Rojansky [email protected]:

Oh OK, didn't read closely enough :) Thanks for commenting in any case.

—
Reply to this email directly or view it on GitHub<
https://github.com/npgsql/Npgsql/issues/132#issuecomment-31023527>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/132#issuecomment-31028856
.

from npgsql.

Sounds good to me too!

Am 21 Dec 2013 um 15:50 schrieb "Francisco Figueiredo Jr." [email protected]:

+1

Excellent, Glen!
Em 20/12/2013 16:02, "Glen Parker" [email protected] escreveu:

Hi guys,

If there's no objection, I'll bring the bool fix into the 2.0.12 branch,
update for 2.0.14.3, and put a new nuget package out tomorrow.

-Glen

On Fri, Dec 20, 2013 at 8:50 AM, Shay Rojansky [email protected]:

Oh OK, didn't read closely enough :) Thanks for commenting in any case.

—
Reply to this email directly or view it on GitHub<
https://github.com/npgsql/Npgsql/issues/132#issuecomment-31023527>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/132#issuecomment-31028856
.

—
Reply to this email directly or view it on GitHub.

from npgsql.

Glen, I think we should create this nuget package without the policy files in order to avoid the issue #131.
There I propose we create separated nuget packages with the policy files separated. This way it would be used at the developer's discretion.

from npgsql.

OK guys,

The new nuget package is up and listed. I left the policy files out as
discussed.

All of the release files are in my Google Drive.

https://drive.google.com/folderview?id=0B2FgfCPmqcEQUGJYejZjRVFHSm8&usp=sharing

-Glen

On Sat, Dec 21, 2013 at 10:35 AM, Francisco Figueiredo Jr. <
[email protected]> wrote:

Glen, I think we should create this nuget package without the policy files
in order to avoid the issue #131#131.

There I propose we create separated nuget packages with the policy files
separated. This way it would be used at the developer's discretion.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/132#issuecomment-31069125
.

from npgsql.

I've now created the release in github as well and uploaded the files there too.
I'm going to update npgsql.org with the new release...

from npgsql.