Christmas gifts for 2024?…

[sansnom]

🇬🇧 Hi, very simply, I was wondering when the next update of the Affinity Suite, version 2.6, compatible with macOS 15.2 Sequoia, will be released? …

If we go back in time, here are some dates…

First official beta available for developers of macOS 15 Sequoia on June 17, 2024: that's 4 months and 27 days ago today, or 150 days ago.

First final version of macOS 15.0 Sequoia in mid-September 2024: that's 1 month and 21 days ago, or 52 days ago.

So it's early November 2024: will we have a delivery date soon? … And can we hope for an update for Christmas? …

 

🇫🇷 Bonjour, très simplement, je me demandais quand sortirait la prochaine mise à jour de la Suite Affinity, version 2.6, compatible avec macOS 15.2 Sequoia ?…

Si l'on revient en arrière, voici quelques dates…

Première béta officielle disponible pour les développeurs de macOS 15 Sequoia le 17 juin 2024 : cela fait aujourd'hui 4 mois et 27 jours, soit 150 jours.

Première version finale de macOS 15.0 Sequoia à la mi-septembre 2024 : cela fait 1 mois et 21 jours, soit 52 jours.

Nous sommes donc début novembre 2024 : aurons-nous bientôt une date de livraison ?… Et pouvons-nous espérer une mise à jour pour Noël ?…

 

[Pšenda]

Since version 2.6 includes many other functions (not only compatibility with some OS, which a large part of users are not interested in at all), which require thorough testing and possible finishing and corrections before release, the date of its release with the release of some OS is not very relevant.

[sansnom]

@Pšenda: “Since version 2.6 includes many other functions (not only compatibility with some OS, which a large part of users are not interested in at all)…”

?!…

@Pšenda: “…the date of its release with the release of some OS is not very relevant.”

?!…

[HCl]

.

[PaulEC]

6 hours ago, sansnom said:

?!…

Why should the rest of us (users of Windows, iPad and other versions of Mac) care about any correlation between the release of Sequoia and the release of Affinity update 2.6? For the majority of users these two events are totally unrelated!

In other words, why should the release of 2.6 be timed to suit Sequoia users, rather than everyone else? As Pšenda said, there's a lot more included in 2.6 than just improved compatibility with Sonoma, and I for one would prefer the release not to be rushed out just to suit one small group of users!

[jmwellborn]

@PaulEC  Don’t you mean Sequoia, not Sonoma?  

[PaulEC]

2 minutes ago, jmwellborn said:

Don’t you mean Sequoia, not Sonoma?  

Thanks for the correction, but, in all honesty I couldn't really care less what the thing is called, I just wish the people who keep going on about it, would remember that there's a whole load of other people using Affinity as well as them, and that everyone is waiting for bug fixes and new features, not just them! 

[sansnom]

🇬🇧 my post was meant to be humorous and offbeat: there are much more important things in the world right now.
And my post was just an observation about how long it takes Serif to give us a compatibility update with v15.

Afterwards, Serif could have perfectly well only offered, initially and quickly, a “simple” patch (v2.5.6) for compatibility with macOS Sequoia: there are inevitably a large number of users who applied the update to v15.0 and who are blocked today, knowing that Serif has absolutely not communicated (as a precaution) on the obvious incompatibility so noted here and elsewhere.

Finally, we must not forget that developing software is an arduous task and is not a quiet river and that it requires a great many skills. We can only hope that these skills have not been transferred to other activities (Canva) and have not abandoned our dear and magnificent software suite...

And once again, my post was meant to be humorous and offbeat... and we can legitimately ask ourselves questions.

 

🇫🇷 mon post se voulait humoristique et décalé : il y a des choses beaucoup plus importantes dans le monde en ce moment.
Et mon post ne faisait qu'un constat sur le temps que met Serif à nous pondre une mise à jour de compatibilité avec v15.

Après, Serif aurait parfaitement pu ne proposer, dans un premier temps et rapidement, qu'une “simple” correctif (v2.5.6) de compatibilité avec macOS Sequoia : il y a fatalement une grande quantité d'utilisateurs qui ont appliqué la mise à jour en v15.0 et qui sont bloqués aujourd'hui, sachant que Serif n'a absolument pas communiqué (en prévention) sur l'incompatibilité patente tant constatée ici et ailleurs.

Enfin, il ne faut pas oublier aussi que le développement d'un logiciel est une tâche ardue et n'est pas un fleuve tranquille et qu'il demande de très nombreuses compétences. On peut juste espèrer que ces compétences n'ont pas depuis d'autres activités (Canva) et ne délaissent notre chère et si magnifique suite de logiciels...

Et encore une fois, mon post se voulait humoristique et décalé... et on peut légitimement se poser des questions.

[Pšenda]

52 minutes ago, sansnom said:

Serif could have perfectly well only offered, initially and quickly, a “simple” patch (v2.5.6) for compatibility with macOS Sequoia:

Yes, he could have done it, but he didn't - which, as far as I know, was announced in advance. Apparently, your idea of "simple and quick" creation of a single-purpose patch differs from the reality that any release of a version is a very difficult and expensive matter. And apparently also due to the progress of work on new functions, Serif therefore decided to combine this with the release of the next major version.

[jmwellborn]

On 11/7/2024 at 8:42 PM, PaulEC said:

Thanks for the correction, but, in all honesty I couldn't really care less what the thing is called, I just wish the people who keep going on about it, would remember that there's a whole load of other people using Affinity as well as them, and that everyone is waiting for bug fixes and new features, not just them! 

Agreed.  I am of the old school that thinks it isn’t all that wise to jump onto the latest wrinkle, just because it is the latest.  If things are working just fine, why tempt fate?  Of course if one must purchase a new Apple product, one is stuck with this year’s new software, which will be replaced by next year’s, which will be replaced by …. Ad infinitum. I am hanging on to my desktop and good old Ventura for as long as possible.  Just me.

[Pšenda]

5 hours ago, jmwellborn said:

I am of the old school that thinks it isn’t all that wise to jump onto the latest wrinkle, just because it is the latest.

I think it doesn't even have to be old school, but rather common sense. Especially if the computer and applications are used seriously/for work, it is really not reasonable to immediately install new versions (this is doubly true for the OS, especially if the applications used are not even recommended/certified for the given OS) and then be surprised that something went wrong.

[PaulEC]

We're probably going a bit OT, but I find it odd that some people insist on always using the latest beta version, apparently because, in their mind, it's the newest version with new features, and therefore better than the release version. Despite warnings about only using beta versions for testing, and not using them for important/production work, they still do so, then post on the forums bemoaning the fact that they've lost important work, and have upset clients, due to bugs in the beta software!

[Pšenda]

On 11/8/2024 at 7:53 AM, sansnom said:

a “simple” patch (v2.5.6) for compatibility with macOS Sequoia

So the "Christmas gifts for 2024" arrived today 🙂
Apparently there was a delay with the release of version 2.6, so Serif decided to release a patch. But I think this means we won't see 2.6 for a long time.

[sansnom]

Hi @Pšenda, hank you very much for the information that I missed this morning. Glad that Serif is apparently delivering a patch: I will look into the scope modified by this patch. Otherwise, I will consult from a distance the progress of the new functions, especially for Affinity Publisher: not being a programmer, but having some programming knowledge, I have the impression that the development of these new functions is difficult and takes time. Well, let's do it!…

[Komatös]

15 minutes ago, Pšenda said:

Apparently there was a delay with the release of version 2.6

3 minutes ago, sansnom said:

I have the impression that the development of these new functions is difficult and takes time.

It had already been announced that there would be a patch to 2.5.6 before the update to 2.6. And, as 2.6 will also have bug fixes and improvements in addition to new functions, there will be a different update cycle.

[sansnom]

Merry Christmas to all...