> On Oct 28, 2022, at 9:29 AM, Markus Spoettl via Cocoa-dev > <cocoa-dev@lists.apple.com> wrote: > > On 10/28/22 1:40 PM, Mark Allan via Cocoa-dev wrote: >> I've held off upgrading for the same reason. I wonder if it's something to >> do with a >> semantic difference between "is no longer supported" and "is no longer >> possible". Maybe >> what they really mean is "if it appears to work, great, but we can't >> guarantee it, and >> if it fails spectacularly, you're on your own"? > > That would certainly be great to know for sure. And where exactly it would > fail spectacularly (if it did), meaning on the development machine or on a > user's machine running an unsupported-by-Xcode system. We didn't notice that > change and released an update to our app which targets 10.11 as deployment > target. > > Regards > Markus > -- > __________________________________________ > Markus Spoettl > > _______________________________________________ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > Please do not post admin requests or moderator comments to the list. > Contact the moderators at cocoa-dev-admins(at)lists.apple.com > > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/cocoa-dev/chris%40kode54.net > > This email sent to ch...@kode54.net
This requirement appears to have been delayed to 14.1, since 14.0 had to be released before Ventura came out. The hard block is on the macOS 13 SDK, which was pushed back to Xcode 14.1. Xcode 14.0 and 14.0.1 as released on the App Store still include the 12.3 SDK. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
