better
(but frankly, it's not that complex, it's copy-pasting), and feel free
to amend the process.
I understand that you went on without taking this versioning constraint
into consideration, no harm in that. But since we always had sequential
versioning in the history of the project, would
Am 2024-04-10 um 22:01 schrieb Claude Brisson:
Hi team.
Can we clarify a little bit the versioning for the future releases?
My point of view is quite simple: did the engine 4.2 get released? No.
So it should be the next version. If it's not what is intended, I need a
detailed explanation
long as we
are clear that if we didn't get three +1 votes on a build, then it can't be
called a release, and thus is not a released version.
On Wed, Apr 10, 2024 at 1:04 PM Claude Brisson
wrote:
> Hi team.
>
> Can we clarify a little bit the versioning for the future releases?
>
>
Hi team.
Can we clarify a little bit the versioning for the future releases?
My point of view is quite simple: did the engine 4.2 get released? No.
So it should be the next version. If it's not what is intended, I need a
detailed explanation, because I really don't understand Michael response
