POLL: Should I bring the v8 server out earlier (as part of a v7.0.0 release)? #891
Replies: 2 comments 2 replies
-
What would be the overhead of releasing an intermediate version? If releasing this does not add much of a delay to v8, then I'd be happy to have a v7 - otherwise I'd say I'd rather wait for v8 to have that sooner. PS: if I misunderstand this and it is not actually an intermediate version, but rather - releasing the server side first and the client later so that we can already upgrade the server - then I would be ok with that. |
Beta Was this translation helpful? Give feedback.
-
Per the votes at this point, I'm going to start working on a v7 branch, |
Beta Was this translation helpful? Give feedback.
-
To clarify, I've been working on the v8 server and it has some great features, including System.Text.Json support, isolated JSON encoding (which means that it can coexist with other libraries like ABP), more solid testing and improvements around EF Core support, and GeoJSON support at the server level. It supports .NET 8 and EF Core 7 out of the box.
However, there are some downsides. Most notably, there are a bunch of breaking changes associated with the move to System.Text.Json and EF Core 7 that will require everyone that is writing custom repositories to take a look at their code to ensure it is still working.
You can find the code base in the v8 branch.
(Note that the v6 codebase won't go away - I'll branch it and do necessary updates as bugs come in)
This poll will be open until March 2nd. (I'm going to Ecuador and Galapagos on vacation from Feb 19th - Mar 2nd, so I won't be able to act on this until then anyhow)
6 votes ·
Beta Was this translation helpful? Give feedback.
All reactions