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
Description: PGP signature
