libpng 1.8.0 late beta: default branch switch and release preparation

--===============5752692123579752690==
Content-Type: multipart/alternative; boundary="00000000000096dac5063ff7035e"

--00000000000096dac5063ff7035e
Content-Type: text/plain; charset="UTF-8"

This is a re-posting of github.com/pnggroup/libpng/discussions/735

***

Hi everyone,

Following up on the early beta announcement from July
<https://github.com/pnggroup/libpng/discussions/726>: libpng 1.8.0 has been
progressing well, and we've now reached the *late beta* stage!

This is a major milestone. The default branch on GitHub has been switched
from libpng16 to libpng18. This reflects our confidence in the 1.8.0
codebase, and it signals that we're approaching release readiness.

WHAT'S HAPPENING NOW:

   - The libpng18 branch is stable and feature-complete, with APNG support
   fully integrated.
   - The documentation is being reorganized and updated. The *"What's new
   in libpng 1.8"* part is coming up soon.
   - We're still working on code deprecations, code cleanups, and build
   system refactorings and cleanups.

WHAT TO KEEP IN MIND:

   - To the best of our knowledge, the correctness of libpng 1.8.0 beta and
   the correctness of libpng 1.6.51 beta are on par. In other words, there are
   no more known bugs in the upcoming libpng 1.8.0 release than there are in
   the upcoming 1.6.51 release.
   - The 1.6.x line is effectively in maintenance mode. With the
   development work shifted onto 1.8.0, we will cherry-pick commits into 1.6.x
   as needed, but the focus will be almost exclusively on correctness and
   security. On the other hand, the work on 1.8.x line will be merged upward
   to 2.x on a regular basis.

WHAT WE NEED FROM YOU:

*Testing!* If you're using libpng in production (browsers, image tools,
embedded systems), now is the time to test the libpng18 branch with your
configurations. We especially want to hear from:

   - Users with custom build configurations.
   - Projects with platform-specific optimizations.
   - Anyone using libpng in security-critical contexts.

Please report any issues you encounter. The more testing we get now, the
smoother the final release will be.

The finish line is in sight. Stay tuned for the final 1.8.0 release!

Sincerely,
Cosmin

--00000000000096dac5063ff7035e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><p>This is a re-posting of=C2=A0<a href=3D"http://github.c=
om/pnggroup/libpng/discussions/735">github.com/pnggroup/libpng/discussions/=
735</a></p><p>***</p><p dir=3D"auto">Hi everyone,</p>
<p dir=3D"auto">Following up on <a href=3D"https://github.com/pnggroup/libp=
ng/discussions/726">the early beta announcement from July</a>: libpng 1.8.0=
 has been progressing well, and we&#39;ve now reached the <strong>late beta=
</strong> stage!</p>
<p dir=3D"auto">This is a major milestone. The default branch on GitHub has=
 been switched from <code class=3D"gmail-notranslate">libpng16</code> to <c=
ode class=3D"gmail-notranslate">libpng18</code>. This reflects our confiden=
ce in the 1.8.0 codebase, and it signals that we&#39;re approaching release=
 readiness.</p>
<p dir=3D"auto">WHAT&#39;S HAPPENING NOW:</p>
<ul dir=3D"auto"><li>The <code class=3D"gmail-notranslate">libpng18</code> =
branch is stable and feature-complete, with APNG support fully integrated.<=
/li><li>The documentation is being reorganized and updated. The <em>&quot;W=
hat&#39;s new in libpng 1.8&quot;</em> part is coming up soon.</li><li>We&#=
39;re still working on code deprecations, code cleanups, and build system r=
efactorings and cleanups.</li></ul>
<p dir=3D"auto">WHAT TO KEEP IN MIND:</p>
<ul dir=3D"auto"><li>To the best of our knowledge, the correctness of libpn=
g 1.8.0 beta=20
and the correctness of libpng 1.6.51 beta are on par. In other words,=20
there are no more known bugs in the upcoming libpng 1.8.0 release than=20
there are in the upcoming 1.6.51 release.</li><li>The 1.6.x line is effecti=
vely in maintenance mode. With the=20
development work shifted onto 1.8.0, we will cherry-pick commits into=20
1.6.x as needed, but the focus will be almost exclusively on correctness
 and security. On the other hand, the work on 1.8.x line will be merged=20
upward to 2.x on a regular basis.</li></ul>
<p dir=3D"auto">WHAT WE NEED FROM YOU:</p>
<p dir=3D"auto"><strong>Testing!</strong> If you&#39;re using libpng in pro=
duction (browsers, image tools, embedded systems), now is the time to test =
the <code class=3D"gmail-notranslate">libpng18</code> branch with your conf=
igurations. We especially want to hear from:</p>
<ul dir=3D"auto"><li>Users with custom build configurations.</li><li>Projec=
ts with platform-specific optimizations.</li><li>Anyone using libpng in sec=
urity-critical contexts.</li></ul>
<p dir=3D"auto">Please report any issues you encounter. The more testing we=
 get now, the smoother the final release will be.</p>
<p dir=3D"auto">The finish line is in sight. Stay tuned for the final 1.8.0=
 release!</p><p dir=3D"auto">Sincerely,<br>
Cosmin</p></div>

--00000000000096dac5063ff7035e--


--===============5752692123579752690==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============5752692123579752690==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
png-mng-implement mailing list
png-mng-implement-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/png-mng-implement

--===============5752692123579752690==--