public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Cc: cygwin-apps@cygwin.com
Subject: Re: Cygwin x86 end-of-life
Date: Sun, 13 Nov 2022 13:31:02 -0700	[thread overview]
Message-ID: <e38781a8-39c6-eb11-300a-1f52ee81245a@SystematicSw.ab.ca> (raw)
In-Reply-To: <13518d55-4b3c-cefd-166d-d41ec7f1a70d@dronecode.org.uk>

On Fri, 11 Nov 2022 16:16:28 +0000, Jon Turney wrote:
> On 11/11/2022 15:50, Jon Turney wrote:
>> As has previously been announced, Cygwin is dropping support for x86 
>> Windows. Cygwin 3.3.6 is the final version supporting x86 (32-bit) 
>> Windows, and the forthcoming Cygwin 3.4 will be released for x86_64 only.
>> 
>> Concurrent with that, updates to x86 packages will be stopped, and the 
>> Cygwin x86 package repository will be archived.
> 
> I plan to pause package uploads this coming Monday (2022-11-14), before 
> starting the re-organization of the package repository to make this archive.
> 
> When package updates resume (I don't have an ETA, but I expect it will 
> take a few days to attend to all the details), attempts to upload x86 
> packages will be rejected with an error.

>> (Instructions on the special steps needed to install from that archive 
>> will be forthcoming, once we've worked out what they are.)
>> 
>> If you're using x86 Cygwin under WOW64 on a 64-bit Windows OS, please 
>> strongly consider moving to an x86_64 Cygwin installation.
>> 
>> (If you have ARM hardware, we believe that x86_64 Cygwin works correctly 
>> using the x86_64 emulation in Windows 11)
>> 
>> If you're one of the tiny percentage of Cygwin users using x86 Cygwin on 
>> a real x86 Windows OS, don't panic! The current installation will 
>> continue to run on your system. You just won't get any more updates.

Give that it took anyone two months after my notices to this list that grep 
would be issuing warnings, and a month after release, before anyone responded, 
and that includes project leadership, providing less than a week's notice is 
obviously insufficient for most to even notice, given that it appears that many 
may not regularly read this list, have any time this month, be busy, or away on 
business or vacation, for weeks.

This appears to be a fairly major undertaking with previously unanticipated and 
unannounced impacts.
It also appears that detailed plans about what this work entails and impacts 
have not yet been fully worked out, no timeline is available, and the details 
and timeline of what is being done is only just being mentioned on this list, 
and not being detailed here or on the general public list for notice and feedback.

I think it is only fair that full details of the impact and timelines should 
first be worked out for whatever next steps need to be taken, and posted to this 
list, the announce, and general public lists, with sufficient notice before 
taking action.

-- 
Take care. Thanks, Brian Inglis			Calgary, Alberta, Canada

La perfection est atteinte			Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter	not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer	but when there is no more to cut
			-- Antoine de Saint-Exupéry

  parent reply	other threads:[~2022-11-13 20:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cfc30991-0dd0-3308-9aca-df7cf81169aa@dronecode.org.uk>
2022-11-11 16:16 ` Jon Turney
2022-11-11 19:45   ` Thomas Wolff
2022-11-11 19:50     ` Achim Gratz
2022-11-11 20:02       ` Thomas Wolff
2022-11-12 16:08         ` Jon Turney
2022-11-12 16:58           ` Thomas Wolff
2022-11-13 13:58             ` Thomas Wolff
2022-11-13 16:43               ` Achim Gratz
2022-11-13 17:01                 ` Thomas Wolff
2022-11-13 17:07             ` Jon Turney
2022-11-13 19:17               ` Corinna Vinschen
2022-11-14 15:24     ` Andrew Schulman
2022-11-13 20:31   ` Brian Inglis [this message]
2022-11-14 16:25   ` Jon Turney
2022-11-14 17:18     ` Andrew Schulman
2022-11-14 20:16     ` Brian Inglis
2022-11-14 21:29       ` Jason Pyeron
2022-11-18 15:51         ` Jon Turney
2022-11-15 19:14     ` Erwin Waterlander
2022-11-28 13:08     ` Jon Turney
2022-11-21 12:45 Corinna Vinschen
2022-11-22 17:51 ` Brian Inglis
2022-11-22 21:07   ` Achim Gratz
2022-11-23 20:00     ` Brian Inglis

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=e38781a8-39c6-eb11-300a-1f52ee81245a@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin-apps@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).