Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drop NET40 support [DNET774] #713

Closed
firebird-automations opened this issue Jul 25, 2017 · 18 comments
Closed

Drop NET40 support [DNET774] #713

firebird-automations opened this issue Jul 25, 2017 · 18 comments

Comments

@firebird-automations
Copy link

Submitted by: @cincuranet

Replaces DNET762
Block progress on DNET776

@firebird-automations
Copy link
Author

Modified by: @cincuranet

Fix Version: 6.0.0.0 [ 10850 ]

@firebird-automations
Copy link
Author

Modified by: @cincuranet

Link: This issue replaces DNET762 [ DNET762 ]

@firebird-automations
Copy link
Author

@firebird-automations
Copy link
Author

Commented by: André Ziegler (andre.ziegler)

-100

I still need .net 40/XP compatibility until 2019 when support for Windows Embedded 2009 ends.

https://support.microsoft.com/en-us/lifecycle/search?alpha=Windows%20Embedded%20Standard%202009

If you kill .net 4.0 and the provider has a serious issue (after .net 40 was killed) that may cause data corruption I can't update the the fixed version.

Also why do you discuss this on a site which noboby knows?

@firebird-automations
Copy link
Author

Commented by: @cincuranet

It's a standard mailing list that you can find on http://firebirdsql.org site. Exactly the place which everybody knows. And Nabble is a web mirror of that.

If you're willing to put money into supporting .NET 4, I can extend the lifetime of that (you can discuss your intention in the list, if you want). Else I just don't have enough free time to spend on .NET 4 and also all other versions.

@firebird-automations
Copy link
Author

Commented by: André Ziegler (andre.ziegler)

it is so well known that only 2 person replied to it. So I call this unknown place.

Also your statement that .net 4.0 no longer gets updated is wrong. Last .net 4.0 update is from June 2017:

June, 2017 Security Only Update for .NET Framework 4 on WES09 and POSReady 2009 (KB4021915)
http://download.windowsupdate.com/c/csa/csa/secu/2017/05/ndp40-kb4021915-x86_e520b6b35c1e6461d73ace5c130ab7ba077296a6.exe

@firebird-automations
Copy link
Author

Commented by: @cincuranet

But that's a KB for XP Embedded. I'm pretty sure there's dozens of variations MS still supports. And will support for extended support customers. I don't have resources for that, sorry. But you can of course help with that as well. Helping hand is always welcome. Will you step in?

BTW, if you have a better place to discuss things, you're welcome to bring that up. So far the mailing lists and tracker is what Firebird project uses.

@firebird-automations
Copy link
Author

Commented by: André Ziegler (andre.ziegler)

I'm talking all the time about XP Embedded. Windows Embedded 2009 is based on Windows XP and XP only supports up to .net 4.0. 4.5 is not supported on XP, that is why I still need .net 4.0 support for 1 year.

@firebird-automations
Copy link
Author

Commented by: @cincuranet

OK, one week from now I'll drop NET40 from 6.0 onward, unless somebody opens up a discussion here or in the list and contributes in any way for NET40 support.

@firebird-automations
Copy link
Author

Modified by: @cincuranet

status: Open [ 1 ] => In Progress [ 3 ]

@firebird-automations
Copy link
Author

Commented by: André Ziegler (andre.ziegler)

before dropping .net 40 support, move the .net 40 code into an extra maintain branch (5.x) and if later provider versions (6.x) include a fix for a serious issue, backport this to the 5.x branch. I don't need new features, I only need some kind of support until Microsoft drops .net 4.0 support for Windows Embedded systems that are based on XP in January 2019.

@firebird-automations
Copy link
Author

Commented by: @cincuranet

That's already possible via IBPhoenix services (https://www.ibphoenix.com/services). I remember backporting some features to old .NET 2.0 versions.

@firebird-automations
Copy link
Author

Commented by: André Ziegler (andre.ziegler)

I don't want features, I only want fixes for blocking issues to .net 4.0 branch. I can do this on my own, but I need the .net 40 code, so please create a .net 40 branch before killing the code from master.

@firebird-automations
Copy link
Author

Modified by: @cincuranet

Link: This issue block progress on DNET776 [ DNET776 ]

@firebird-automations
Copy link
Author

Commented by: André Ziegler (andre.ziegler)

so what are the plans now? can we get the extra branch for users who still (have to) care about .net 4.0 support for old XP Embedded systems?

@firebird-automations
Copy link
Author

Commented by: @cincuranet

Yes. The 5.x version will be maintained with .NET 4 support, if needed. Current version is tagged https://github.com/cincuranet/FirebirdSql.Data.FirebirdClient/tree/5.11.0.0. 6.x will drop it.

@firebird-automations
Copy link
Author

Modified by: @cincuranet

status: In Progress [ 3 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

@firebird-automations
Copy link
Author

Modified by: @cincuranet

summary: Drop NET40 support => Drop NET40 support #⁠breaking

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment