On Nov 13 17:07, Jon Turney wrote: > On 12/11/2022 16:58, Thomas Wolff wrote: > > Am 12.11.2022 um 17:08 schrieb Jon Turney: > > > On 11/11/2022 20:02, Thomas Wolff wrote: > > > > Am 11.11.2022 um 20:50 schrieb Achim Gratz: > > > > > Thomas Wolff writes: > > > > > > > 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. > > > > > > Although expected for a while, the exact date is now a very > > > > > > short-time > > > > > > announcement. Can we have a moratorium for a short while? > > > > > > So, if not now, when? > > Well, first, I think it's not a good idea to change and over-interpret a > > plan in this way. The announcement for a year or so has been "cygwin 3.4 > > will not support 32 bit anymore". This does not imply that the > > repository will be closed so any other package would not be allowed > > anymore to provide updates. What about security updates? Basic > > functionality? > > Security is a complete red-herring here. We are not good at making timely > updates for that purpose, generally. To suggest that x86 will be receiving > security updates, when we've also said x86 is deprecated, and some > maintainers aren't updating it at all, makes no sense at all. > > The message needs to be: If you care about security, at the very least, > don't use x86 Cygwin. This is one of the reasons why I want to archive x86. > > If you think there is some broken "basic functionality" in the current > package set, please say what it is. If something critical is discovered > after the freeze, I am not totally ruling out permitting an exceptional > upload (although the case for criticality would have to be well made, as, > again this involves yet more work for me, to benefit a small percentage of > installations, and one would think that such critical problems would be > evident currently).
Well said. Corinna
