tree c4af3e2df64acb98628af4f675d2160622c21423
parent 27df725179045a2e91a34eb91e29e52d0fe5f663
author Clark Boylan <clark.boylan@gmail.com> 1494609393 -0700
committer Clark Boylan <clark.boylan@gmail.com> 1494609393 -0700

Document testing of new devstack features

At the Boston 2017 Summit I had mentioned that the pattern of using non
voting/experimental jobs was not working for getting new features into
Devstack. It is slow and leads people to being too conservative when it
comes to pushing new things in. Instead I suggested that since Devstack
changes are self testing we add the features, have change that enables
the feature, and if that changes passes we move forward with merging
(assuming code review is fine and necessary communication is done).

Document this process in the HACKING file so that we have something we
can point to when people want to add a new experimental job for every
new little thing (ipv6, tls, systemd, etc).

Change-Id: I5190cc3d3de4e81d52748347306133b5034d5531