Re: new release?
Sam James <[email protected]>
| Newsgroups | gmane.comp.gnu.libtool.general |
|---|---|
| Message-ID | <20220208030121.16e9f2fa@zen> |
On Sun, 6 Feb 2022 12:21:34 -0600 (CST) Bob Friesenhahn <[email protected]> wrote: > On Sun, 6 Feb 2022, Daniel Herring wrote: > > > > In my opinion, frequent slow releases are way better than rare fast > > releases. > > That may be true for some software, but libtool has a really good > test suite so if tests pass, there is high confidence of quality for > the systems it has been executed on. It is abnoxiously painful to > build libtool starting from git sources so hardly anyone is testing > the unreleased code. > > Pushing out a release assures that the mechanics are working and that > it is even possible to create a release. > > Users are much more apt to report bugs and patches against software > that they can easily use. Yep! Especially given that distros are obviously going to be careful with testing libtool, even more so given they (we!) know development is resuming after a long haitus, and we're checking which of our patches are still relevant, etc. It's not like it'll be bumped downstream without anybody doing due diligence :) best, sam
signature.asc
(application/pgp-signature, 618 B)
-----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEYOpPv/uDUzOcqtTy9JIoEO6gSDsFAmIB3QFfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYw RUE0RkJGRkI4MzUzMzM5Q0FBRDRGMkY0OTIyODEwRUVBMDQ4M0IACgkQ9JIoEO6g SDtiSAf/ZTDq1/qFKSfnq5aPUI0cF8nDn4OG1a9ZwaW3dCadP6A3bbx+/QlVXxZp 5H5CKIA+JWh+y8xpwiqk09wnsH3hhpKwyTyLpUBBqzqpcpXgds+pTvdYFU2mEAwl uo+Y1sHB2oIONBz3KCEeLoeoMAxHnvrBD+gkneKdkzleoYBFas0cm/YUAjTluCTv 0XPMCqymXdDw0krcU9ncdg+ToNwxW3KmjOXwaGOzSQM1/r5RSEEfsL/6K/lCydRk B4dCFtC+374GMpsxH90YLzXm5uKwMuqgTVDOPJTQCofsWtBTKk0ln5wIlzTwtXQN JsyLsWyPgwmO7EdJIbfwRRlgkhDhgA== =69kz -----END PGP SIGNATURE-----