Date: Thu, 11 Dec 2025 09:36:06 +0000 From: Sad Clouds <cryintothebluesky@gmail.com> To: Lexi Winter <ivy@freebsd.org> Cc: questions@freebsd.org Subject: Re: Trying to understand base system packages Message-ID: <20251211093606.eade25c5f5c65277120d2f6e@gmail.com> In-Reply-To: <aToOxuaXNTa5LOOP@amaryllis.le-fay.org> References: <20251205122830.cb88058f193987b47a95a77c@gmail.com> <20251205134510.6fae5caf@dorfdsl.de> <20251205143119.441cc1bd8722345d074a4480@gmail.com> <16e766b9-f442-4cef-a991-c940f6b8182a@gmail.com> <20251207081139.7e2f65b97b4c089ac0add431@gmail.com> <aTkvIvFJHLf4WxUa@amaryllis.le-fay.org> <aTm6mdWQ_nyv21El@rain.cave> <20251210203319.c248921c4e6aca9ba07458ae@gmail.com> <aToOxuaXNTa5LOOP@amaryllis.le-fay.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 11 Dec 2025 00:22:30 +0000 Lexi Winter <ivy@freebsd.org> wrote: > the entire FreeBSD system is "still undergoing development and design > changes", yet we still ship releases every year. There are many different software development processes and I guess each one has its pros and cons. I personally prefer the traditional software life cycle: requirements, design, implementation, testing, deployment. The advantage is that you are less likely to release half-baked solutions and any issues found during implementation or testing can be pushed back to the re-design stage without exposing any of the mess to the end users. So for me "production software" means: all aspects of the requirements + design + implementation are complete, documentation is complete, and all unit and integration tests are complete and we have close to 100% test coverage. There is nothing wrong with the iterative process and many projects take this approach. However I used to work in a commercial software development environment and had a really bad experience with the Agile process that was forced upon everyone in the company. People were "harassed" by clueless managers to release some feature every two weeks and we often released buggy and half-baked software, which was poorly tested and lacked extensive documentation. Part of the problem was that some complex features took 6 months or more to implement and were difficult to fully implement and verify in smaller parts because of the various inter dependencies.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20251211093606.eade25c5f5c65277120d2f6e>