> On Sep 28, 2021, at 3:37 AM, Masakazu Kitajo <mas...@apache.org> 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 pick those PRs which should go into 9.2.x.
> 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.
Agreed. v9.2.x is not “feature frozen” yet, but will be. We can certainly pick
a hard date for this if that’s the community concsent?
>
> I'm personally going to suspend reviewing PRs for 10.0, PRs that try to add
> new features to 9.x, and PRs that try to resolve issues on previous
> releases (except security issues).
Hmmm, what PRs does that leave then? ;-). Everyone should review all 10.0.x
(master) PRs, only those PRs landed on master would ever be considered going
into any 9.x release. I can understand not reviewing PRs going into “10-Dev”,
those are the invasive / incompatible PRs that we want for 10.0.0, but which
can not go into 9.x.
Cheers,
— Leif
>
> Masakazu
>
> On Sat, Sep 18, 2021 at 1:52 AM Leif Hedstrom <zw...@apache.org> wrote:
>
>> 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 November /
>> early December, or possibly early January 2022. Please discuss if you have
>> a preference here.
>>
>> Cheers,
>>
>> — Leif
>>
>>
