<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">I am glad we have a new release, but
there remains a version checking concern:<br>
<br>
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
<a class="moz-txt-link-freetext" href="http://erlang.org/pipermail/erlang-questions/2014-March/077998.html">http://erlang.org/pipermail/erlang-questions/2014-March/077998.html</a>).
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 <span class="code">erlang:system_info()</span> argument
giving the exact OTP version. This since the exact OTP version in
the general case is hard to determine."
(<a class="moz-txt-link-freetext" href="http://www.erlang.org/doc/man/erlang.html#system_info-1">http://www.erlang.org/doc/man/erlang.html#system_info-1</a>). 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
(<a class="moz-txt-link-freetext" href="http://www.erlang.org/doc/system_principles/versions.html">http://www.erlang.org/doc/system_principles/versions.html</a>) 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?<br>
<br>
Thanks,<br>
Michael<br>
<br>
On 04/09/2014 08:24 AM, Kenneth Lundin wrote:<br>
</div>
<blockquote
cite="mid:CAOzgw93zqHxgmbX+cjv2npztNfun-jc68UQodkRO+UPBzEBpDw@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>Erlang/OTP 17.0 <span></span>has been released.<br>
</div>
<div class="gmail_quote">
<div dir="ltr">
<div class="gmail_quote">
<div dir="ltr">
<div class="gmail_quote">
<div dir="ltr">
<div class="gmail_quote">
<div>
<div>
<div dir="ltr">
<div class="gmail_quote">
<div dir="ltr">
<div>
<div>
<br>
Erlang/OTP 17.0 is a new major
release with new features,
characteristics improvements, as
well as some minor
incompatibilities. <br>
<br>
</div>
<div>
<div class="h5">Some highlights of
the release are:
<ul>
<div>
<li> Erlang/OTP has been
ported to the realtime
operating system OSE.</li>
<li> Maps, a new dictionary
data type (experimental)</li>
<li> A more natural mapping
from ASN.1 OCTET STRING and
BIT STRING to Erlang types,
and other ASN.1 improvements
and optimizations</li>
<li> The {active, N} socket
option for TCP, UDP, and
SCTP</li>
<li> A new (optional)
scheduler utilization
balancing mechanism</li>
<li> Migration of memory
carriers has been enabled by
default on all ERTS internal
memory allocators</li>
<li> Increased garbage
collection tenure rate</li>
<li> Experimental "dirty
schedulers" functionality</li>
<li> Funs can now be given
names</li>
<li> Miscellaneous unicode
support enhancements</li>
</div>
<li>A new version scheme for OTP
its applications has been
introduced</li>
</ul>
<div>
<p> You can find the README file
with more detailed info at <a
moz-do-not-send="true"
href="http://www.erlang.org/download/otp_src_17.0.readme"
target="_blank">http://www.erlang.org/download/otp_src_17.0<span></span>.readme</a></p>
<p> You can download the full
source distribution from <a
moz-do-not-send="true"
href="http://www.erlang.org/download/otp_src_17.0.tar.gz"
target="_blank">http://www.erlang.org/download/otp_src_17.0<span></span>.tar.gz</a></p>
</div>
</div>
</div>
</div>
<div>
<div class="h5">
<div>
<p> Note: To unpack the TAR
archive you need a GNU TAR
compatible program. For
installation instructions please
<span></span>read the README
that is part of the
distribution.</p>
</div>
<div>
<p> You can also find this release
at the official Erlang/OTP
Git-repository at Github here: <a
moz-do-not-send="true"
href="https://github.com/erlang/otp"
target="_blank">https://github.com/erlang/otp</a>
tagged "OTP-17.0"<span></span></p>
<div>
<p> The Windows binary
distribution can be downloaded
from</p>
<p> <a moz-do-not-send="true"
href="http://www.erlang.org/download/otp_win32_17.0.exe"
target="_blank">http://www.erlang.org/download/otp_win32_17.0<span></span>.exe</a>
<br>
</p>
<p><a moz-do-not-send="true"
href="http://www.erlang.org/download/otp_win64_17.0.exe"
target="_blank">
http://www.erlang.org/download/otp_win64_17.0.exe
</a></p>
<p> You can also download the
complete HTML documentation or
the Unix manual files <br>
</p>
<p><a moz-do-not-send="true"
href="http://www.erlang.org/download/otp_doc_html_17.0.tar.gz"
target="_blank">http://www.erlang.org/download/otp_doc_html_17.0<span></span>.tar.gz</a>
<br>
<a moz-do-not-send="true"
href="http://www.erlang.org/download/otp_doc_man_17.0.tar.gz"
target="_blank">http://www.erlang.org/download/otp_doc_man_17.0<span></span>.tar.gz</a></p>
<p> We also want to thank those
that sent us patches,
suggestions and bug reports.</p>
<p> The Erlang/OTP Team at
Ericsson</p>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
</div>
</div>
</div>
</div>
<br>
</div>
</div>
<br>
</div>
</div>
<br>
</div>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
erlang-questions mailing list
<a class="moz-txt-link-abbreviated" href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a>
<a class="moz-txt-link-freetext" href="http://erlang.org/mailman/listinfo/erlang-questions">http://erlang.org/mailman/listinfo/erlang-questions</a>
</pre>
</blockquote>
<br>
</body>
</html>