Today we released the first beta of Npgsql 2.0.13!
This new beta release had a lot of bugs fixed and initial support for Entity Framework 6! More information about how to use Entity framework 6 with Npgsql can be found in this post.
Checkout the release notes for more information about the bugs fixed in this release.
Download it from our downloads section.
Important notice about this release
Unfortunately, I made a mistake when updating the assembly version for this release and it was created with a wrong value. I'm very sorry for that.
This release should have been 22.214.171.124 and not 126.96.36.199
Next beta release will have the version value fixed.
What are the implications?
The biggest problem is that this beta version will have a version number higher than the final 2.0.13 version while this beta version has 188.8.131.52. As it is a beta and it is not supposed to be deployed in production systems, we think this won't give problems to our users. We are very sorry for any problem this may have caused.
How is Npgsql assembly versioned?
In the beginning, we used to use the same assembly version througout all the beta release cycle until the final release.
With this approach, Npgsql 2.0.10 beta1 would have the assembly version of 184.108.40.206 and beta2 would also have the assembly version of 220.127.116.11. This was creating confusion between users because they couldn't differentiate which version they were working with.
Starting with 2.0.11, we changed this in order to identify each version. We started to use the last two parts of the assembly version in order to identify beta releases.
This way, a beta release was identified in the following form:
- Npgsql 2.0.11 beta1 would be identified as: 18.104.22.168;
- Npgsql 2.0.11 beta2 would be identified as 22.214.171.124 and so on.
With this schema, the beta versions will be incremented towards the final version 126.96.36.199.
Regarding this 2.0.13 beta1 release, its assembly version should have been 188.8.131.52 and not 184.108.40.206. The former value indicates the assembly is approaching the 2.0.13 while the latter indicates the assembly is approaching 2.0.14 which is not the case.
We hope this won't happen again. :(