For what it’s worth, I’m fine with both formal branching-level freeze and
informal ‘let people commit to trunk if they can find a reviewer’ one and will
support either.
So long as either/both are communicated to the contributors, the only
difference is in where new feature work gets accumulated
Actually taking back my +1, seems like we've got a fair amount of dtests
(at least 7) failing consistently on 2.2, and another one that's very flaky.
Last completed runs are here:
https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-2.2-dtest/116/testReport/
https://builds.apache.org/vie
+1
On 02.07.2018 22:10, Michael Shuler wrote:
> I propose the following artifacts for release as 2.2.13.
>
> sha1: 9ff78249a0a5e87bd04bf9804ef1a3b29b5e1645
> Git:
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.13-tentative
>
> Artifacts:
> https://repository.
