Re: new release?

On 06 Feb 2022 11:56, Daniel Herring wrote:
> FWIW, libtool is a particularly difficult code base to release.  Long 
> history, many users, multi-platform, ...
> 
> I would personally recommend the "slow" process unless you are confident 
> this release will "do no harm".  It was made for a reason, even if it 
> feels nobody is participating.  Relax, practice the release process, 
> spread the news and give people time to respond, build a good reputation, 
> have cover in case bugs are found later, ...

no software is ever bug free.  being paralyzed by "is it ready yet" and
never making a release as a result makes the problem worse.  infrequent
releases tend to lead to large accumulation of changes which makes them
even more unstable because the interactions are never tested.

libtool has a testsuite.  if bugs are found, fix them, add more tests.
iterate and move on.
-mike

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEuQK1JxMl+JKsJRrUQWM7n+g39YEFAmIAF30ACgkQQWM7n+g3
9YH3sBAAkQg80Mim3/Frcn83ntZy5mt2I89MU+t8ZNPEh6oJPE5e3Rb+FkrnuMmX
Ta0orUuXBXaPoideSCi4d632kU77Sl5ua+ZMaflvLNKUtGbzdgMoiIyrOFoy5Big
/iJx5lyYTIbIR900vOq2u0Ws+mUoRy/iOysCFzqATuKXDAVhxfU4IPzOH0x5guft
mlMfBw6n/c6r7gC6FPSrRk4/NehyvgE9srEA+j2qC+90v9DKILcFhm7vDfKlzf5P
KVRYkTj5eArApRBtDQheJAoslDoNYEMurx2VUCeBKWHS25zyrNfCYVK+Gn+DP17E
pB7zfctJ0CspB1kcMcUvGJZbELb1nyL1cK50oJK36IlX6moc1dowYb1+5mNW4U7f
lBSwsjFT2SMQI14gSwrAVNiTGl58HZnBG7J1abhP2zEAtzlZyOXSNR9Ux5hQhWaI
z3Fc0srL2ovnIec29kx7V3zISGM6cvyv/eI659TN9hJJhi+UR1ZoGrp1lU86gm6M
GDwZvHeg5Js+9m+98Bc39wXVgYqT/YoKGjzHfGgOklSXFHWSkmrPQXB/EiJrcC6m
M2aIohjbuhr0B1goZ06m2aExVONvuz1Hds1mtkB+P4uQB36+7xSh2y3d5aUCxC3j
qh5+H0vOJbn1QtsOY0KnU6uUxGboSmmLOx4RZjCc8onUZyFH1Gc=
=s89C
-----END PGP SIGNATURE-----