Dear Alain, Thanks for your message.
For Scilab users, incompatibility mainly comes from functions renaming, removal or incompatible prototype change. In the past, this kind of change could even occur in patch versions (which could be released more than once a year). With this new release schedule and numbering, our aim is not to break compatibility more often. We just want to clarify what will be the contents of releases and when they will be available (containing incompatibilities or not). Vincent -----Original Message----- From: users <users-boun...@lists.scilab.org> On Behalf Of Lamy Alain Sent: Wednesday, February 22, 2023 11:07 AM To: users@lists.scilab.org Subject: Re: [Scilab-users] [Scilab-Dev] Scilab releases schedule / End of Windows 32-bit support Dear Scilab users / team, Just one opinion among others: That's nice to have new Scilab releases regularly, provided of course that backward compatibility is guaranteed us much as possible, except maybe for major versions. But I don't see the need for changing the versioning convention. For instance knowing that Scilab version is 5.x.x or 6.x.x is major information that is easy to notice at a glance. That's not the case if the version major number becomes a year number. And it let people think that the version from some given year could potentially be incompatible with the version from the previous year, which is not good news. Alain Lamy _______________________________________________ users mailing list - users@lists.scilab.org Click here to unsubscribe: <mailto:users-unsubscr...@lists.scilab.org> https://lists.scilab.org/mailman/listinfo/users _______________________________________________ users mailing list - users@lists.scilab.org Click here to unsubscribe: <mailto:users-unsubscr...@lists.scilab.org> https://lists.scilab.org/mailman/listinfo/users This email and any attachments are intended solely for the use of the individual or entity to whom it is addressed and may be confidential and/or privileged. If you are not one of the named recipients or have received this email in error, (i) you should not read, disclose, or copy it, (ii) please notify sender of your receipt by reply email and delete this email and all attachments, (iii) Dassault Systèmes does not accept or assume any liability or responsibility for any use of or reliance on this email. Please be informed that your personal data are processed according to our data privacy policy as described on our website. Should you have any questions related to personal data protection, please contact 3DS Data Protection Officer https://www.3ds.com/privacy-policy/contact/
