Maybe wait until the NDA is lifted and then ask the questions you need to? Waiting until the 16th shouldn’t be a huge delay?
André-John Sent from my phone. Envoyé depuis mon téléphone. > On 12 Sep 2024, at 16:53, [email protected] wrote: > > I’m not worried by Sequoia in itself, I’ve used .0s before and usually with > good luck (it seems I use way fewer weird software than the typical user). > I’m just worried that some of the ports I need are broken with the new > compiler (tbh, macports in my experience are often the most susceptible to > macOS version changing). > Anyway, I was just asking if some especially bad problem was apparent in > testing, and may be a way to filter the bugs for sequoia (I couldn’t find it). > > Ciao, > gt > > PS: btw, yeah, a ‘sacrificial’ computer is a good idea I’ll do it… thank you! > >> On 12 Sep 2024, at 22:45, André-John Mas <[email protected]> wrote: >> >> If you are worried then best wait for a .1 release, that way anything that >> didn’t get in QA will be found by the general public. >> >> At the same time, if you are needing a feature that only exists on the >> latest release, then I’d recommend getting a second ‘sacrificial’ computer. >> >> André-John >> >> Sent from my phone. Envoyé depuis mon téléphone. >> >>>> On 12 Sep 2024, at 16:32, [email protected] wrote: >>> >>> I was just wondering if there is an easy way to check for lingering bugs >>> on macOS Sequoia before upgrading… I need it for a project but I’m always >>> worried about ports… (yes, I know that all will be compiled locally for a >>> while)… I don’t think the NDA (if any exists anymore) forbids talking about >>> that, if yes, sorry… >>> Thank you in advance, >>> gt >
