delorie.com/archives/browse.cgi | search |
> Clearly, master is always more likely to have bugs, as a result of > integration of new features (patch commit or merge - whatever), but I think > it is always best to TRY and keep master in a state where we expect it > works, and expect we COULD branch a release from it. True, but there's a wide range of options (and paranoia levels) between "good enough to play with" and "good enough to release". What I don't want is to make it so difficult and/or expensive to get work into master, that work never gets into master. We need to be willing to accept *some* risk in order to promote progress.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |