> On Sep 29, 2021, at 2:10 AM, Masakazu Kitajo wrote:
>
> I'm not sure if we are on the same page. We review PRs for master. The
> process itself stays the same. I'm trying to say we should refrain from
> making changes that are not going to be cherry-picked to 9.2.x branch until
> we release
I'm not sure if we are on the same page. We review PRs for master. The
process itself stays the same. I'm trying to say we should refrain from
making changes that are not going to be cherry-picked to 9.2.x branch until
we release 9.2.0. If you find a regression on 9.2.x, you can make a PR for
maste
Well, we shouldn’t merge PRs to master which are not properly reviewed. If the
consensus is that we stop merging on master until 9.2.x is stable, then that
would make sense. But then again, how do we fix things then for 9.2.x or other
versions if no one is reviewing master branch PRs. I’ll leave
I understand all changes has to be landed on master first and that's fine,
but active development for future releases (9.3 or 10.0) on master after
branching 9.2.x increase the gap between the two and cherry-picking gets
difficult day by day. "10-Dev" branch probably mitigate it, but I don't see
re
> On Sep 28, 2021, at 3:37 AM, Masakazu Kitajo wrote:
>
> Can you clarify what branching 9.2.x means (again)?
It means, branched from master -> 9.2.x. Going forward, anything that we want
in 9.2.x must be marked with “Project 9.2.x” (remember, Milestone is still
10.0.0), and I will cherry p
Can you clarify what branching 9.2.x means (again)?
I don't have a strong opinion on the release date, but I think RM should
clearly call a feature freeze sooner rather than later and we all should
focus on stabilizing the branch because we already have many changes for
9.2.0.
I'm personally goin
Hi all,
I’m going to branch v9.2.x, from current master, Monday morning, 9/20. We will
continue development on v9.2.0 of course, but remember that you will need to
mark PRs with “Project 9.2.x” for consideration into the upcoming branch. I’d
like to aim to have a v9.2.0 release either late Nove