Also, as has been already mentioned, the year version may or may not imply an actual major version (i.e., changes that imply an important or significant API change, which not necessarily means backward incompatibility) so to find out it will be necessary to dive into the change log. The only new information the proposed version numbering system would give is the year of release which is only relevant for historical reasons (and anyway can be easily found). Moreover, for most users (those who use the current version at a given time), it would be a redundant information since users know the year they live in.
Regards, Federico Miyara On 22/02/2023 07:07, Lamy Alain wrote: 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<mailto:users@lists.scilab.org> Click here to unsubscribe: <mailto:users-unsubscr...@lists.scilab.org><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/ ________________________________ [Avast logo] <https://www.avast.com/antivirus> El software de antivirus Avast ha analizado este correo electrónico en busca de virus. www.avast.com<https://www.avast.com/antivirus> 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/
_______________________________________________ users mailing list - users@lists.scilab.org Click here to unsubscribe: <mailto:users-unsubscr...@lists.scilab.org> https://lists.scilab.org/mailman/listinfo/users
