4 ms·
I grew up in the open source community. There's a lot of really good best practices that you pick up there as you contribute to or pull from other projects. Amo
by peterwwillis 13y ago
I grew up in the open source community. There's a lot of really good best practices that you pick up there as you contribute to or pull from other projects. Among those are the development/stable release trees.
If you have something that "just works", you do a release, but to a development branch. Eventually some of those features can get backported to stable, or the release will get upgraded to stable after thorough testing, or all new feature development will end once it's been tested enough to ensure a stable release. There may be 10 development releases before a stable release comes out. The benefit is you get to "just ship" code, but stable users aren't forced to deal with your bugs and various changes just because you wanted to get an experimental feature out the door.
"To ship" is not a software development practice. It's silicon valley hype. It's the idea that delivering an average product is more important than designing, developing, testing, and producing a really good product. The author is right, this is difficult. But this is not what I think most people consider when they say "to ship".