From: Patrick Robb <probb@iol.unh.edu>
To: Tyler Retzlaff <roretzla@linux.microsoft.com>
Cc: ci@dpdk.org, Stephen Hemminger <stephen@networkplumber.org>
Subject: Windows Server 2019 in UNH CI Testing?
Date: Thu, 25 Jul 2024 15:14:37 -0400 [thread overview]
Message-ID: <CAJvnSUB4_fRxt+ykDXgo+ZDi6vUqPAguwYVeWmkKFK1OFfNTqg@mail.gmail.com> (raw)
Hello Tyler,
Windows Server 2019 mainstream end of support date is January 2024,
and extended end of support date is January 2029.
Currently at UNH we have two VMs (windows server 2019 and 2022) both
running the Clang-LLVM & MinGW-64 compile jobs.
The server 2022 machine also runs the custom MSVC compile jobs that we
set up in Fall 2023.
So, with Windows Server 2019 reaching end of regular support, should
we discontinue CI on this system, or maintain it until (potentially)
2029 when it reaches end of extended support?
I am okay with either, I just don't necessarily understand how
significant the regular vs extended support distinction is, and
whether the results from the older system are still valuable for
developers.
Cheers.
-Patrick
https://learn.microsoft.com/en-us/lifecycle/products/windows-server-2019
next reply other threads:[~2024-07-25 19:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 19:14 Patrick Robb [this message]
2024-07-25 21:53 ` Stephen Hemminger
2024-08-06 5:43 ` Tyler Retzlaff
2024-08-06 16:38 ` Patrick Robb
2024-08-06 16:47 ` Tyler Retzlaff
2024-08-06 17:10 ` Patrick Robb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJvnSUB4_fRxt+ykDXgo+ZDi6vUqPAguwYVeWmkKFK1OFfNTqg@mail.gmail.com \
--to=probb@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=roretzla@linux.microsoft.com \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).