Npgsql 3.0

[Shay Rojansky]

Hey everyone.

We've been discussing that the next release of Npgsql should be a major one - 3.0 - and that we should use this opportunity to get rid of legacy features and behavior, even if it introduces some breakage. The logic is if breakage needs to be introduced, 3.0 is exactly the place to do so, so this is a good opportunity.

• Map the Postgresql type TimestampTZ to DateTimeOffset and not to DateTime (#11).
• Remove support for .NET 2.0 and .NET 3.0 (#320)
• Eliminate the preload reader (#312)
• Possibly the reorganization of logging in Npgsql (#279)
  
• Some of the work on async may involve refactoring; it shouldn't involve breakage but it may be a risky/big change (#121)

This is a good time to think about other things we should be getting rid of, or legacy behavior which was kept only because changing it would be breakage. Francisco and Josh, you guys are probably the ones with the best historical perspective here...

[Francisco Figueiredo Jr.]

Excellent, Shay!

I think you got everything. Breaking changes wise, I don't remember what else would be good to go in 3.0.

I'll check pgfoundry forums to see if there is anything I may be forgetting.

[Josh Cooley]

We've had requests for names and namespace changes, but I'm not inclined to do that since I don't see the value in that.

--
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/d/optout.

[Shay Rojansky]

It's true Npgsql could use a namespace cleanup, but I tend to agree it's probably not worth breaking people's code just for that...