I support removal of vs2015 and 2017. Since ci only builds and tests n (vs2022). Supporting n-1 (vs2019) is already just on faith and with the idea that reported failures will be fixed.

I also agree with dropping previously deprecated tags. Thanks for the effort.

Thanks

Sean

From: discuss@edk2.groups.io <discuss@edk2.groups.io> on behalf of Rebecca Cran <rebecca@bsdio.com>
Sent: Tuesday, October 22, 2024 4:18:51 AM
To: devel@edk2.groups.io <devel@edk2.groups.io>; discuss@edk2.groups.io <discuss@edk2.groups.io>
Cc: Liming Gao <gaoliming@byosoft.com.cn>; Michael D Kinney <michael.d.kinney@intel.com>; Oliver Smith-Denny <osde@linux.microsoft.com>
Subject: [edk2-discuss] Removal of VS2015 (and maybe VS2017) and deprecated toolchains (GCC48, GCC49, GCC5)

With the addition of VS2022 I'd like to propose removing VS2015, and
discuss whether people think it might be suitable to also remove VS2017
too, from tools_def.txt.

Back in July, Oliver sent the following message:

"Per Liming's request I am moving this discussion to the mailing list.
Now that VS2022 support has been added to edk2, can we drop VS2015
support (honestly VS2017 could be dropped, too). This is an almost
10 year old toolchain that is unsupported, has many quirks, and will
continue to require odd changes from new code to support it, for no
gain. VS2015 (and 2017) users should move to VS2022."

In addition, since GCC48, GCC49 and GCC5 have been marked deprecated for
over a year, I'd like to proceed with removing them as well.

Please provide feedback by Thursday October 31st. In the absence of
feedback I'll plan to proceed with removing VS2015, GCC48, GCC49 and GCC5.

--
Rebecca Cran