On 2018-05-31 00:21:35 +0000 (+0000), Fox, Kevin M wrote: > To play devils advocate and as someone that has had to git bisect > an ugly regression once I still think its important not to break > trunk. It can be much harder to deal with difficult issues like > that if trunk frequently breaks. [...]
Agreed. We made a choice as a community early on to avoid doing that. (Almost) always deployable is (almost) always testable; if trunk is broken, then as a developer working on a bugfix or new feature you have to hunt for a known-working state in the history to develop against and then rebase onto all the broken and cross your fingers that you're not making the job of whoever has to untangle trunk before release that much harder. -- Jeremy Stanley
signature.asc
Description: PGP signature
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
