Patrick Connor

We are planning to release a 2.3.1 patch to address a handful of important things and then start 2.4.0 beta.
We think it's important to address a few high customer impact bugs quickly in a 2.3.1 release, in a fast/stable manner.
The release of 2.4.0 with improvements and features and many fixes will likely take a while to be "release ready" (need a longer beta testing cycle due to having more significant code changes).
We have builds for both 2.3.1 and 2.4.0 in internal testing at the moment. I would expect these to both be with you in the first half of this month

We are planning to release a 2.3.1 patch to address a handful of important things and then start 2.4.0 beta.
We think it's important to address a few high customer impact bugs quickly in a 2.3.1 release, in a fast/stable manner.
The release of 2.4.0 with improvements and features and many fixes will likely take a while to be "release ready" (need a longer beta testing cycle due to having more significant code changes).
We have builds for both 2.3.1 and 2.4.0 in internal testing at the moment. I would expect these to both be with you in the first half of this month

We are planning to release a 2.3.1 patch to address a handful of important things and then start 2.4.0 beta.
We think it's important to address a few high customer impact bugs quickly in a 2.3.1 release, in a fast/stable manner.
The release of 2.4.0 with improvements and features and many fixes will likely take a while to be "release ready" (need a longer beta testing cycle due to having more significant code changes).
We have builds for both 2.3.1 and 2.4.0 in internal testing at the moment. I would expect these to both be with you in the first half of this month

We are planning to release a 2.3.1 patch to address a handful of important things and then start 2.4.0 beta.
We think it's important to address a few high customer impact bugs quickly in a 2.3.1 release, in a fast/stable manner.
The release of 2.4.0 with improvements and features and many fixes will likely take a while to be "release ready" (need a longer beta testing cycle due to having more significant code changes).
We have builds for both 2.3.1 and 2.4.0 in internal testing at the moment. I would expect these to both be with you in the first half of this month

We are planning to release a 2.3.1 patch to address a handful of important things and then start 2.4.0 beta.
We think it's important to address a few high customer impact bugs quickly in a 2.3.1 release, in a fast/stable manner.
The release of 2.4.0 with improvements and features and many fixes will likely take a while to be "release ready" (need a longer beta testing cycle due to having more significant code changes).
We have builds for both 2.3.1 and 2.4.0 in internal testing at the moment. I would expect these to both be with you in the first half of this month

We are planning to release a 2.3.1 patch to address a handful of important things and then start 2.4.0 beta.
We think it's important to address a few high customer impact bugs quickly in a 2.3.1 release, in a fast/stable manner.
The release of 2.4.0 with improvements and features and many fixes will likely take a while to be "release ready" (need a longer beta testing cycle due to having more significant code changes).
We have builds for both 2.3.1 and 2.4.0 in internal testing at the moment. I would expect these to both be with you in the first half of this month

We are planning to release a 2.3.1 patch to address a handful of important things and then start 2.4.0 beta.
We think it's important to address a few high customer impact bugs quickly in a 2.3.1 release, in a fast/stable manner.
The release of 2.4.0 with improvements and features and many fixes will likely take a while to be "release ready" (need a longer beta testing cycle due to having more significant code changes).
We have builds for both 2.3.1 and 2.4.0 in internal testing at the moment. I would expect these to both be with you in the first half of this month

We are planning to release a 2.3.1 patch to address a handful of important things and then start 2.4.0 beta.
We think it's important to address a few high customer impact bugs quickly in a 2.3.1 release, in a fast/stable manner.
The release of 2.4.0 with improvements and features and many fixes will likely take a while to be "release ready" (need a longer beta testing cycle due to having more significant code changes).
We have builds for both 2.3.1 and 2.4.0 in internal testing at the moment. I would expect these to both be with you in the first half of this month

We are planning to release a 2.3.1 patch to address a handful of important things and then start 2.4.0 beta.
We think it's important to address a few high customer impact bugs quickly in a 2.3.1 release, in a fast/stable manner.
The release of 2.4.0 with improvements and features and many fixes will likely take a while to be "release ready" (need a longer beta testing cycle due to having more significant code changes).
We have builds for both 2.3.1 and 2.4.0 in internal testing at the moment. I would expect these to both be with you in the first half of this month

We are planning to release a 2.3.1 patch to address a handful of important things and then start 2.4.0 beta.
We think it's important to address a few high customer impact bugs quickly in a 2.3.1 release, in a fast/stable manner.
The release of 2.4.0 with improvements and features and many fixes will likely take a while to be "release ready" (need a longer beta testing cycle due to having more significant code changes).
We have builds for both 2.3.1 and 2.4.0 in internal testing at the moment. I would expect these to both be with you in the first half of this month

We are planning to release a 2.3.1 patch to address a handful of important things and then start 2.4.0 beta.
We think it's important to address a few high customer impact bugs quickly in a 2.3.1 release, in a fast/stable manner.
The release of 2.4.0 with improvements and features and many fixes will likely take a while to be "release ready" (need a longer beta testing cycle due to having more significant code changes).
We have builds for both 2.3.1 and 2.4.0 in internal testing at the moment. I would expect these to both be with you in the first half of this month

We are planning to release a 2.3.1 patch to address a handful of important things and then start 2.4.0 beta.
We think it's important to address a few high customer impact bugs quickly in a 2.3.1 release, in a fast/stable manner.
The release of 2.4.0 with improvements and features and many fixes will likely take a while to be "release ready" (need a longer beta testing cycle due to having more significant code changes).
We have builds for both 2.3.1 and 2.4.0 in internal testing at the moment. I would expect these to both be with you in the first half of this month

...any yet you post in here about A4 frames. That is spamming/trolling. You have made your point about the first post in this thread so there is no need to keep posting in here

Do you think I have nothing better to do than be here on Boxing day 😅

No this is not happening, and you realising that these new forums would be the place for you to post means you must now accept that there is no existing place for you to post these comments.  

...any yet you post in here about A4 frames. That is spamming/trolling. You have made your point about the first post in this thread so there is no need to keep posting in here

...any yet you post in here about A4 frames. That is spamming/trolling. You have made your point about the first post in this thread so there is no need to keep posting in here

No this is not happening, and you realising that these new forums would be the place for you to post means you must now accept that there is no existing place for you to post these comments.  

No this is not happening, and you realising that these new forums would be the place for you to post means you must now accept that there is no existing place for you to post these comments.  

No this is not happening, and you realising that these new forums would be the place for you to post means you must now accept that there is no existing place for you to post these comments.  

...any yet you post in here about A4 frames. That is spamming/trolling. You have made your point about the first post in this thread so there is no need to keep posting in here

No this is not happening, and you realising that these new forums would be the place for you to post means you must now accept that there is no existing place for you to post these comments.  

Do you think I have nothing better to do than be here on Boxing day 😅

If you are a new arrival to this thread and have found that it is locked but still want to show your support for Affinity on Linux, simply like this post

This years contemplative and thoughtful "New Year's Eve" firework impressions ...

... used for some online cards, with the help from some of my firework assets.
Some Firework assets
 
Stop the wars and have instead a peaceful and hopefully then world wide much better new year!