Re: new release?
Mike Frysinger <[email protected]>
| Newsgroups | gmane.comp.gnu.libtool.general |
|---|---|
| Message-ID | <Yf8tMRCmPvyhs/zH@vapier> |
On 05 Feb 2022 15:15, Alex Ameen wrote: > This is a good question. I plan on making a new release this month. > > When I first adopted the project I ambitiously thought I'd manage to > create a new release after about a month; but the truth is when I > started doing a deep dive into the internals there was a lot of history > and complexity for me to unpack. Things that are easy to overlook like > how change-logs get generated, quirks in the testing framework, and > tracing down disparate areas to align documentation took quite a while > to navigate. > > The good news is that I think I've got the confidence to push a release > soon. One area that I was reading up on this weekend was whether the > "alpha"/private releases of `libtool' might be appropriate, or whether I > should just push a release immediately. I'll admit I am leaning towards > just making a release to avoid the entire alpha process for the time being. i wouldn't sweat it too much. the next release of libtool will be 2.6, and you can note its state in the announcement/NEWS. distros will give it a run to find regressions, and as fixes are merged, just do 2.6.1, 2.6.2, etc... -mike
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEuQK1JxMl+JKsJRrUQWM7n+g39YEFAmH/LTAACgkQQWM7n+g3 9YELARAArdLVfIEmlPvGM8jves+85CpHmihDzL6+5OSPOAdMsdKmGylda4+mT0O7 gk8iSfyeAk/210u/0dRJ53dywTcn8YPKlz6338hj9m1wi0Hc3hxBSWXsERP2tC+X UmOlUeLm6rbecS97wwlrvDPMIyRSin0LcVqnHDQkqZE60K3BgppoAiQH+JhlOgLX 0o4AEIUDp3Kdl22QL5x36rculmVg2GmKKAxjVWCioR38eCmeusX/52+6bDKrCBiT /dTwecaijz4Ozm5OMJnCrFRV4y5wYfDn9uyZFAiUhR0Pwido/xuijZp1zmukgwUO df4GJsM7eIRKp8hFifxJtryeHzIBFO7uDKpY4I4c/PxaosqwVsEfZ03+W0/INwDU iVFyP4Je3OS9GZRO2PVB+0Ivb6Ww8xbgvJHWNTuj1V15URa79ks1u+WTAYWby4zV SquaDLaAEeImaf9x63ARmnECkdstjCrIuRIt3+DNdCzvSp+b3FUxDZ60MRKY0A8Z sAeqct8++q91sPicBHSyc5TTzt+gbhudxOVLnNDG5d3cXC1wxfD0xZQtZ1m4oB0j pm+vOOeIhXGKW+KV5/fClVymXWii0KaVl5KDstTdYKwCoiyxY47La6kcjSxPRJ8w 2yEqSUDIbCix+2D/752ygFMUSJoGAl3oDsR8kXv3wiV/R4bNRdk= =R4Pl -----END PGP SIGNATURE-----