search

endoflife-date / endoflife.date

Informative site with EoL dates of everything
https://endoflife.date
MIT License
2.41k stars 737 forks source link

Add Internet Explorer #1316

Closed Evernow closed 2 years ago

Evernow commented 2 years ago

Sources used for end of life dates:

Individual releases: https://docs.microsoft.com/en-us/lifecycle/products/?products=internet-explorer

https://docs.microsoft.com/en-us/lifecycle/faq/internet-explorer-microsoft-edge#what-is-the-lifecycle-policy-for-internet-explorer-

Exception for Explorer 7 is due to it being part of Windows Embedded: https://docs.microsoft.com/en-us/lifecycle/products/internet-explorer-7

Evernow commented 2 years ago

I assume that the next Windows Server will be based on Windows 11, which doesn't support Internet Explorer. As such Windows Server 2022 should be the last Windows release to support Explorer, as a result we won't have to update this entry again in theory.

usta commented 2 years ago

For the Record I am against this PR ( Dont get it wrong @Evernow , and thank you for your hard work )

The reason why we dont need to add Internet Explorer into end of life site : 1- It is never been updatable with users/admins choice 2- Users couldnt choice not to install it 3- Users/Admins couldnt uninstall/remove it 4- The product itself finished i mean it wont be another IE (Internet explorer any more) 5- If we start to add products which wont be exist any newer version we will have lots of trash in here just like adding Adobe Flash or Netscape 6- If any of you really wish to add this ( shame of internet)[product] (again thank you micro$oft) we need to add it not as a standalone category/product but as in under Microsoft Edge ( if dont know if we have it or not )

So My vote is not Adding IE ( it was always a shame and it will needs to be forgotten quickly )

What are your opinions ? @BiNZGi @captn3m0 @hebbet

captn3m0 commented 2 years ago

Want to make a few changes in the text, but overall looks good 👍🏼. Thanks for the quick PR.

We ought to include this based on the Be Helpful guiding principle.

It's currently supported, and will be for 9 more years in some cases - having this might be useful to some users.

Too many softwares is our problem to solve in a better way regardless (categorisation etc).

hugovk commented 2 years ago

I disagree with a blanket statement saying IE11 is supported until 2031, that won't help our users as it's more nuanced than that.

Internet Explorer 11 follows the Component Lifecycle Policy.

The Internet Explorer (IE) 11 desktop application will end support for Windows 10 semi-annual channel starting June 15, 2022.

https://docs.microsoft.com/en-us/lifecycle/products/internet-explorer-11

It's true some Windows server and point-of-sale operating systems will support IE11 for longer, and we can include that.

But it's fair to say that our biggest user group will be web developers for "normal" computers, and for them IE11 is EOL tomorrow, not in 2031.

So I recommend listing each relevant OS in brackets after 11, and one per row.

This could be useful because it's difficult to find on the MS website.

ESU is not normal EOL:

The Extended Security Update (ESU) program is a last resort option for customers who need to run certain legacy Microsoft products past the end of support.

And if we're listing ESU dates, these should be explicitly noted as such, and the standard EOL dates also included.

Evernow commented 2 years ago

So I recommend listing each relevant OS in brackets after 11, and one per row.

This would be in my opinion too cluttered, especially since from what I can see there are 17 releases of Windows still supporting Internet Explorer in one way or the other, with likely more changes once you start to account for their respective minor releases

This could be useful because it's difficult to find on the MS website.

ESU is not normal EOL:

The Extended Security Update (ESU) program is a last resort option for customers who need to run certain legacy Microsoft products past the end of support.

And if we're listing ESU dates, these should be explicitly noted as such, and the standard EOL dates also included.

But it's fair to say that our biggest user group will be web developers for "normal" computers, and for them IE11 is EOL tomorrow, not in 2031.

Hence why "11 (Semi-Annual Channel)" is a releaseCycle and there are notes at the bottom clarifying what this means.

we're listing ESU dates, these should be explicitly noted as such, and the standard EOL dates also included

Again I personally think this would be too cluttered, I believe saying "It's 2031 unless you have a Windows installation that is end of life before then" is enough here. I think it's fairly obvious for the type of people who are still using this that Internet Explorer is not supported on Windows 7, just because of the fact that Windows 7 is not supported at all (except for ESU)

Evernow commented 2 years ago

@usta

For the Record I am against this PR ( Dont get it wrong @Evernow , and thank you for your hard work )

I somewhat agree with you, only reason I opened this PR is because it was requested and will no active involvement on our part.

Still though, it is a somewhat common misconception that "Internet Explorer is dead for good now", while in practice it is, it's still available for those who desperately need it on some Windows releases .

hugovk commented 2 years ago

So I recommend listing each relevant OS in brackets after 11, and one per row.

This would be in my opinion too cluttered, especially since from what I can see there are 17 releases of Windows still supporting Internet Explorer in one way or the other, with likely more changes once you start to account for their respective minor releases

Oh yeah, 17 would be too much. Are there just a handful that share the same dates? Could they be grouped in rows?

Evernow commented 2 years ago

So I recommend listing each relevant OS in brackets after 11, and one per row.

This would be in my opinion too cluttered, especially since from what I can see there are 17 releases of Windows still supporting Internet Explorer in one way or the other, with likely more changes once you start to account for their respective minor releases

Oh yeah, 17 would be too much. Are there just a handful that share the same dates? Could they be grouped in rows?

Dates relevant from what I can see, removing duplicates:

Windows 7 ESU: January 10, 2023

Windows 8.1: July 11, 2023

Windows 10 2015 LTSB: Oct 14, 2025

Windows 10 2016 LTSB/Server 2012: Oct 13, 2026

Windows 10 2019 LTSB/Server 2019 : Jan 9, 2029

Server 2008 (this varies by edition, only listing latest one): January 10, 2023

Server 2016: January 12, 2027

Server 2022: October 14, 2031

Windows Embedded Standard 7/Embedded Compact 2013 : Oct 10, 2023

Note I did not go through each phases, for example I am listing only the ESU dates where applicable, not the end of Mainstream support for a given release. Listing both (which we should if we go with this approach) would increase the amount of releases significantly.

hugovk commented 2 years ago

As it stands, I think this is misleading:

image

It should be much clearer that for the vast majority of developers and users, IE11 is already EOL.

I also don't think we should treat paid, extended "last resort" (in Microsoft's own words) support as a "normal" EOL. It's fine to list both, but make it clear.

Evernow commented 2 years ago

As it stands, I think this is misleading:

I agree with you, maybe the 2031 entry can be listed as 

11 (Enterprise support)

And the 2022 EOL entry can be:

11 (Consumer)

That would make it quite clear who this applies for, and we can further clarify what these terms mean at the bottom. I believe it would also be fairly accurate since Windows server, LTSB and the embedded platforms are mainly meant for commercial applications.

BiNZGi commented 2 years ago

My proposal:

-   releaseCycle: "11-ltsb"
    releaseLabel: "11 LTSB/LTSC/Server"
    eol: 2031-10-14
    releaseDate: 2013-11-13

-   releaseCycle: "11"
    eol: 2022-06-14
    releaseDate: 2013-11-13
Evernow commented 2 years ago

My proposal:

-   releaseCycle: "11-ltsb"
    releaseLabel: "11 LTSB/LTSC/Server"
    eol: 2031-10-14
    releaseDate: 2013-11-13

-   releaseCycle: "11"
    eol: 2022-06-14
    releaseDate: 2013-11-13

Good enough for me, although it also needs to include embedded.

usta commented 2 years ago

@BiNZGi Can we change 14-june-2022 to 15-june-2022 as like it is written in m$ website : image https://www.microsoft.com/en-us/download/internet-explorer.aspx

Evernow commented 2 years ago

@BiNZGi Can we change 14-june-2022 to 15-june-2022 as like it is written in m$ website : image https://www.microsoft.com/en-us/download/internet-explorer.aspx

This was discussed before: https://github.com/endoflife-date/endoflife.date/pull/1316#discussion_r896404894

BiNZGi commented 2 years ago

@usta already discussed in comments @Evernow thanks for pointing out