[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: new release?
From: |
Mike Frysinger |
Subject: |
Re: new release? |
Date: |
Sun, 6 Feb 2022 13:46:21 -0500 |
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
signature.asc
Description: PGP signature
- new release?, Werner LEMBERG, 2022/02/02
- Re: new release?, Alex Ameen, 2022/02/05
- Re: new release?, Mike Frysinger, 2022/02/05
- Re: new release?, Richard Purdie, 2022/02/06
- Re: new release?, Daniel Herring, 2022/02/06
- Re: new release?, Alexei Podtelezhnikov, 2022/02/06
- Re: new release?, Bob Friesenhahn, 2022/02/06
- Re: new release?, Sam James, 2022/02/08
- Re: new release?,
Mike Frysinger <=
- Re: new release?, Frederic Berat, 2022/02/07
- Re: new release?, Alex Ameen, 2022/02/07
- Re: new release?, Daniel Herring, 2022/02/07
- Re: new release?, Sam James, 2022/02/08
Re: new release?, Roumen Petrov, 2022/02/08