[erlang-questions] [ANN] Erlang/OTP 17.0 has been released

Michael Truog <>
Wed Apr 9 23:53:25 CEST 2014


I am glad we have a new release, but there remains a version checking concern:

I am a bit concerned the new versioning with 17.0 (not the release candidates) doesn't provide the minor release number.  This goes beyond the fact the erlang:system_info(otp_correction_package) removal breaks existing version checking source code (as was mentioned here http://erlang.org/pipermail/erlang-questions/2014-March/077998.html). I understand the html doc says "As of OTP release 17, the OTP release number corresponds to the major OTP version number. There is no erlang:system_info() argument giving the exact OTP version. This since the exact OTP version in the general case is hard to determine." (http://www.erlang.org/doc/man/erlang.html#system_info-1).  This could force the error-prone parsing of erlang:system_info(system_version) to get the release candidate number in the future, but the minor release number remains missing.  Isn't the minor release number required for support issues, to understand what anyone has installed?  The current documentation wants people 
to make custom OTP_VERSION file in their target system (http://www.erlang.org/doc/system_principles/versions.html) but that isn't part of the installation, so it is in no way a standard, just an obscure detail.  How should we deal with understanding what has changed in a minor release?

Thanks,
Michael

On 04/09/2014 08:24 AM, Kenneth Lundin wrote:
> Erlang/OTP 17.0 has been released.
>
> Erlang/OTP 17.0 is a new major release with new features, characteristics improvements, as well as some minor incompatibilities.
>
> Some highlights of the release are:
>
>   * Erlang/OTP has been ported to the realtime operating system OSE.
>   * Maps, a new dictionary data type (experimental)
>   * A more natural mapping from ASN.1 OCTET STRING and BIT STRING to Erlang types, and other ASN.1 improvements and optimizations
>   * The {active, N} socket option for TCP, UDP, and SCTP
>   * A new (optional) scheduler utilization balancing mechanism
>   * Migration of memory carriers has been enabled by default on all ERTS internal memory allocators
>   * Increased garbage collection tenure rate
>   * Experimental "dirty schedulers" functionality
>   * Funs can now be given names
>   * Miscellaneous unicode support enhancements
>   * A new version scheme for OTP its applications has been introduced
>
> You can find the README file with more detailed info at http://www.erlang.org/download/otp_src_17.0.readme <http://www.erlang.org/download/otp_src_17.0.readme>
>
> You can download the full source distribution from http://www.erlang.org/download/otp_src_17.0.tar.gz <http://www.erlang.org/download/otp_src_17.0.tar.gz>
>
> Note: To unpack the TAR archive you need a GNU TAR compatible program. For installation instructions please read the README that is part of the distribution.
>
> You can also find this release at the official Erlang/OTP Git-repository at Github here: https://github.com/erlang/otp tagged "OTP-17.0"
>
> The Windows binary distribution can be downloaded from
>
> http://www.erlang.org/download/otp_win32_17.0.exe <http://www.erlang.org/download/otp_win32_17.0.exe>
>
> http://www.erlang.org/download/otp_win64_17.0.exe <http://www.erlang.org/download/otp_win64_17.0.exe>
>
> You can also download the complete HTML documentation or the Unix manual files
>
> http://www.erlang.org/download/otp_doc_html_17.0.tar.gz <http://www.erlang.org/download/otp_doc_html_17.0.tar.gz>
> http://www.erlang.org/download/otp_doc_man_17.0.tar.gz <http://www.erlang.org/download/otp_doc_man_17.0.tar.gz>
>
> We also want to thank those that sent us patches, suggestions and bug reports.
>
> The Erlang/OTP Team at Ericsson
>
>
>
>
>
>
>
>
> _______________________________________________
> erlang-questions mailing list
> 
> http://erlang.org/mailman/listinfo/erlang-questions

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20140409/8787c856/attachment.html>


More information about the erlang-questions mailing list