Thanks, - How do you deal with patch releases of earlier versions (such as for a security issue raised in a CVE)? Will you be making 2024.m.p releases in 2025? If not, will you tell linux distributions to upgrade major? - If an API breaking change must be released, it can only happen as the first release of the next year?
Best, On Fri, Feb 17, 2023 at 6:13 PM COUVERT Vincent <vincent.couv...@3ds.com<mailto:vincent.couv...@3ds.com>> wrote: Hi Sylvain, The semantic meaning of major/minor/patch version is kept: - Major releases may have API changes: o There may be API changes between Scilab 2023.m.p and 2024.m’.p’ but it is not mandatory - Minor releases are API compatible: o Changes between Scilab 2023.m.p and Scilab 2023.m’.p’ cannot be related API changes - Patches are binary compatible: o Changes between Scilab 2023.m.p and Scilab 2023.m.p’ will not involve binary change. Changes on p (patch) mostly concern “hot fixes”. Compatibility with other tools (Matlab, Office, Excel, …) and even OS following the same calendar will be easier to follow and understand. This new release schedule also allows us to give a better visibility to developers/contributors in order to anticipate: - API changes, - Function deprecation, - Maintenance periods, - Scilab evolutions. >From a user perspective, it will be easier to identify how up-to-date or >deprecated their Scilab could be. Vincent From: dev <dev-boun...@lists.scilab.org<mailto:dev-boun...@lists.scilab.org>> On Behalf Of Sylvain Corlay Sent: Friday, February 17, 2023 4:04 PM To: List dedicated to the development of Scilab <dev@lists.scilab.org<mailto:dev@lists.scilab.org>> Subject: Re: [Scilab-Dev] Scilab releases schedule / End of Windows 32-bit support Hi Vincent, The problem with year-based versioning is that it removes any semantic meaning to minor and patch - especially with respect to relinking etc. What are the expected benefits of the proposed change ? Best, On Fri, Feb 17, 2023 at 4:01 PM COUVERT Vincent <vincent.couv...@3ds.com<mailto:vincent.couv...@3ds.com>> wrote: Hi Sylvain, Thanks for your email, we completely agree with you about the meaning and contents of major, minor and patch versions. As you say, “Major version updates may break API compatibility” but it is not mandatory for a major version. As in the past, we will try to not break compatibility between versions (whatever the version type is) but if we have to do it, we will do it in major versions (planned for October) and try to warn users asap. Best regards, Vincent From: dev <dev-boun...@lists.scilab.org<mailto:dev-boun...@lists.scilab.org>> On Behalf Of Sylvain Corlay Sent: Thursday, February 16, 2023 4:57 PM To: List dedicated to the development of Scilab <dev@lists.scilab.org<mailto:dev@lists.scilab.org>> Subject: Re: [Scilab-Dev] Scilab releases schedule / End of Windows 32-bit support Hi Vincent, Thank you for the updates and the new releases. I think that one potential issue with such a versioning scheme is the communication of backward compatibility of APIs and ABIs. A commonly accepted schemas is to have Major.major.patch schema where, 1. Patch version updates are binary compatible This means that if you built B and linked with A version M.m.x, you can install A version M.m.y with y>=x without any issue. 2. Minor version updates are API compatible This means that you can rebuild B without changing its code against the new version of A. 2. Major version updates may break API compatibility This means that you may need to update the code of B if you make use of APIs of A. Year-based versioning prevents making deductions based on the version number. While it may be possible to infer such information based on sonames, the semantics of sonames are platform dependent (incompatible between OS X and Linux), and very easy to get wrong. Conda-forge makes heavy use of the M.m.p pattern, especially in the "run_exports" mechanism which allows it to have a working rolling distribution. Best, Sylvain On Thu, Feb 16, 2023 at 4:42 PM COUVERT Vincent <vincent.couv...@3ds.com<mailto:vincent.couv...@3ds.com>> wrote: Hi all, Scilab operational team and contributors are working hard on next release of Scilab that will be available in the next weeks. In the future, we will follow a new 6-month release schedule and use a new release numbering system X.Y.Z based on years: - 2023.0.0 very soon (as we did not release a version in October 2022) - 2023.1.0 in May 2023 - 2024.0.0 in October 2023 - 2024.1.0 in May 2024 - And so on… Minor versions will be released as needed between these planned versions and will only contain “hot fixes” with no new features, no function prototype change, … Releasing Scilab X.2.Z will probably never happen but remains possible. Since we no more have hardware resources to validate it, we will not release a 32-bit version of future Scilab releases for Windows (Linux 32-bit versions are no more available since Scilab 6.0.0). Best regards, Scilab operational team 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/ _______________________________________________ dev mailing list dev@lists.scilab.org<mailto:dev@lists.scilab.org> https://lists.scilab.org/mailman/listinfo/dev 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/ _______________________________________________ dev mailing list dev@lists.scilab.org<mailto:dev@lists.scilab.org> https://lists.scilab.org/mailman/listinfo/dev 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/ _______________________________________________ dev mailing list dev@lists.scilab.org<mailto:dev@lists.scilab.org> https://lists.scilab.org/mailman/listinfo/dev 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/
_______________________________________________ dev mailing list dev@lists.scilab.org https://lists.scilab.org/mailman/listinfo/dev
