John Howard 773205214e Remove releaselocks/ (#2288) ... We currently have two redundant ways to test for breaking changes in proto: proto-commit and releaselocks. These do the same thing, but add substantial noise. Release locks have also not been updated since 1.6. The original intent was to test for breaking changes between versions. However, since we test for breaking changes on each commit, there is no need for the extra check; if it would have failed as "breaking change from 1.0 -> HEAD" then it would also fail with "breaking change from HEAD^ -> HEAD". Finally, there are some weird LC_ALL issues with sorting that make the releaselocks really hard to use, especially for newcomers. I spent hours trying to fix it without success		2022-03-17 15:29:43 -07:00
..
release-1.5	Remove releaselocks/ (#2288)	2022-03-17 15:29:43 -07:00
release-1.6	Remove releaselocks/ (#2288)	2022-03-17 15:29:43 -07:00