Il 24/10/2016 22:15, Nyall Dawson ha scritto:
> +1. It's confusing since people are opening PRs against master_2 when as
> far as I know this branch is a dead end.
It makes sense to me. Any reason not to close it immediately?
Also, I'd close commits for 2.16, and mark is as unmaintained. Keeping
On 24 Oct 2016 10:35 PM, "Sandro Santilli" wrote:
>
> Now that 2.18 is out and its release-2_18 branch was created,
> and given the decision for 2.18 to be the last release in
> the 2.x series, should the "master_2" be removed ?
+1. It's confusing since people are opening PRs
Now that 2.18 is out and its release-2_18 branch was created,
and given the decision for 2.18 to be the last release in
the 2.x series, should the "master_2" be removed ?
And maybe the roadmap table [1] should be updated to add
3.0 release ?
[1]