<div dir="ltr"><div dir="ltr">Well I can see it among the erlang/otp releases and the URL to it is here<br><a href="https://github.com/erlang/otp/archive/OTP-21.3.2.tar.gz">https://github.com/erlang/otp/archive/OTP-21.3.2.tar.gz</a><br><br></div><div>This is something that github creates automatically for every git tag<br><br></div><div>/Kenneth Erlang/OTP<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Mar 22, 2019 at 9:19 AM Frank Muller <<a href="mailto:frank.muller.erl@gmail.com">frank.muller.erl@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div dir="auto">Why I can’t see 21.3.2 tarball release on GitHub (like 21.2.7)?</div></div><div dir="auto"><br></div><div dir="auto">Thank you</div><div dir="auto">/Frank</div><div dir="auto"><br></div><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Patch Package: OTP 21.3.2<br>
Git Tag: OTP-21.3.2<br>
Date: 2019-03-21<br>
Trouble Report Id: OTP-15684, OTP-15685, OTP-15688, OTP-15690<br>
Seq num: ERL-475, ERL-837<br>
System: OTP<br>
Release: 21<br>
Application: erts-10.3.1, xmerl-1.3.20<br>
Predecessor: OTP 21.3.1<br>
<br>
Check out the git tag OTP-21.3.2, and build a full OTP system<br>
including documentation. Apply one or more applications from this<br>
build as patches to your installation using the 'otp_patch_apply'<br>
tool. For information on install requirements, see descriptions for<br>
each application version below.<br>
<br>
---------------------------------------------------------------------<br>
--- erts-10.3.1 -----------------------------------------------------<br>
---------------------------------------------------------------------<br>
<br>
Note! The erts-10.3.1 application can *not* be applied independently<br>
of other applications on an arbitrary OTP 21 installation.<br>
<br>
On a full OTP 21 installation, also the following runtime<br>
dependencies have to be satisfied:<br>
-- kernel-6.1 (first satisfied in OTP 21.1)<br>
-- sasl-3.3 (first satisfied in OTP 21.2)<br>
<br>
<br>
--- Fixed Bugs and Malfunctions ---<br>
<br>
OTP-15688 Application(s): erts<br>
<br>
If a suspend/resume signal pair was sent to a process<br>
while it was executing dirty, the receiving process<br>
could later end up in a suspended state indefinitely.<br>
This bug was introduced in ERTS version 10.0 (OTP<br>
21.0).<br>
<br>
Suspend/resume signals are sent from<br>
erlang:suspend_process()/erlang:resume_process(). The<br>
dbg trace tool utilize this functionality and could<br>
thus trigger this bug.<br>
<br>
<br>
OTP-15690 Application(s): erts<br>
Related Id(s): PR-2172<br>
<br>
Fix a possible deadlock when terminating the ERTS<br>
caused by a dirty scheduler not releasing it's<br>
run-queue lock when terminating.<br>
<br>
<br>
Full runtime dependencies of erts-10.3.1: kernel-6.1, sasl-3.3,<br>
stdlib-3.5<br>
<br>
<br>
---------------------------------------------------------------------<br>
--- xmerl-1.3.20 ----------------------------------------------------<br>
---------------------------------------------------------------------<br>
<br>
The xmerl-1.3.20 application can be applied independently of other<br>
applications on a full OTP 21 installation.<br>
<br>
--- Fixed Bugs and Malfunctions ---<br>
<br>
OTP-15684 Application(s): xmerl<br>
Related Id(s): ERL-837<br>
<br>
Handling of character references in attributes are<br>
fixed.<br>
<br>
<br>
OTP-15685 Application(s): xmerl<br>
Related Id(s): ERL-475<br>
<br>
Normalization of whitespace characters in attributes<br>
are fixed so it works when character references are<br>
used.<br>
<br>
<br>
Full runtime dependencies of xmerl-1.3.20: erts-6.0, kernel-3.0,<br>
stdlib-2.5<br>
<br>
<br>
---------------------------------------------------------------------<br>
---------------------------------------------------------------------<br>
---------------------------------------------------------------------<br>
<br>
_______________________________________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@erlang.org</a><br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
</blockquote></div></div>
_______________________________________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@erlang.org</a><br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
</blockquote></div>