From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [HEADSUP] Phasing out old Windows versions and 32 bit support
Date: Wed, 27 Oct 2021 10:53:58 +0200 [thread overview]
Message-ID: <YXkTpuC1WG86ZKbN@calimero.vinschen.de> (raw)
In-Reply-To: <20211027042947.GS32501@ming.fruitbat.org>
On Oct 26 21:29, Peter A. Castro wrote:
> On Tue, Oct 26, 2021 at 06:52:02PM -0400, Michel LaBarre wrote:
>
> Greetings, Michel & Corinna,
>
> > Corinna , thank you for the heads up regarding subsequent updates wrt Window
> > 7.
> >
> > Would it be possible to create a short "how-to" for installing the most
> > recently "known-to-work-with-Windows-7" version of Cygwin (presuming that
> > old versions remain accessible indefinitely...). Alternately, how one can
> > download a repository now that is compatible with Windows 7 and useable for
> > installing Cygwin in anticipation of the upcoming loss of support.
>
> As these milestones occur I will make notes in the Cygwin Time Machine
> concerning the ending release snapshot and installers, like what I have
> for the last XP release.
>
> Corinna, I presume you will post when these milestones occur so that we
> have a more exact message in the Cygwin mail archive?
In which way do you mean? My planning was this:
When I release 3.3.0 (next couple of days), I will add a note to the
announcement that this is the last major release supporting Vista and
Server 2008.
When I release 3.4.0 (in some nebular future of 2022), I will add a
note to the announcement that this version does not support Vista and
2008 anymore, and that 3.4.0 is the last version supporting
W7, 8, 2008R2, 2012.
That ok? Or do you think of somehting else?
Oh, that reminds me... I should have sent the headsup to cygwin-announce,
not to the cygwin ML. I will fix this omission immediately...
Thanks,
Corinna
next prev parent reply other threads:[~2021-10-27 8:54 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 20:55 Corinna Vinschen
2021-10-26 22:01 ` [QUAR] " Eliot Moss
2021-10-26 22:52 ` Michel LaBarre
2021-10-27 4:29 ` Peter A. Castro
2021-10-27 8:53 ` Corinna Vinschen [this message]
2021-10-27 16:28 ` Peter A. Castro
2021-10-28 7:00 ` Corinna Vinschen
2021-10-27 14:57 ` Michel LaBarre
2021-10-27 16:38 ` Peter A. Castro
2021-10-27 8:33 ` Corinna Vinschen
2021-10-27 0:24 ` Takashi Yano
2021-10-27 8:49 ` Corinna Vinschen
2021-10-27 9:37 ` Thomas Wolff
2021-10-27 10:20 ` Corinna Vinschen
2021-10-27 16:46 ` Peter A. Castro
2021-10-27 21:04 ` Thomas Wolff
2021-10-27 23:35 ` Peter A. Castro
2021-10-27 13:07 ` Andrew Schulman
2021-10-27 11:03 ` L A Walsh
2021-10-27 11:10 ` Corinna Vinschen
2021-10-27 15:25 ` [HEADSUP] " Jim Reisert AD1C
2021-10-27 17:22 ` EXTERNAL: " Damon Register
2021-10-27 22:35 ` [HEADSUP] Phasing out old Windows versions and 32 bit support [XEmacs for 64-bit?] Dan Harkless
2021-10-27 22:37 ` Dan Harkless
2021-10-27 22:36 ` Dan Harkless
2021-10-28 8:47 ` Henry S. Thompson
2021-10-27 20:36 [HEADSUP] Phasing out old Windows versions and 32 bit support Jeremy Drake
2021-10-28 6:00 ` Brian Inglis
2021-10-28 7:11 ` Corinna Vinschen
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=YXkTpuC1WG86ZKbN@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).