Hi, Michael and Haiting,
Thanks for your suggestions, I’ve updated the PR, PTAL.
Thanks,
Yunze
> On Sep 8, 2022, at 14:41, Haiting Jiang wrote:
>
> Good point, Michael.
>
> Compile errors happen quite often when cherry-picking commits, even
> though there is no conflict
> but compile still
Good point, Michael.
Compile errors happen quite often when cherry-picking commits, even
though there is no conflict
but compile still may fail due to some dependency PR missing, or when
we try to resolve some
simple conflicts.
Thanks,
Haiting
On Thu, Sep 8, 2022 at 2:26 AM Michael Marshall wr
> If the PR can be cherry-picked directly, we should also check the
> CI status of the branch after we push them directly.
In order to catch basic compilation or checkstyle errors, I always run
the following before pushing a cherry picked commit to an upstream
branch:
mvn -Pcore-modules,-main -T
Good suggestion. I will update in the PR soon.
Thanks,
Yunze
> On Sep 6, 2022, at 15:46, Haiting Jiang wrote:
>
> There are a lot of work before current release process, maybe we should
> also include these:
>
> 1. Start a discussion on the mail list about the release. We can provide a
> te
Great work! Yunze.
There are a lot of work before current release process, maybe we should
also include these:
1. Start a discussion on the mail list about the release. We can provide a
template to include more clear info about opening PRs and PRs to be
cherry-picked to the released branch.
2.
Hi Yu,
Thanks for your reminder@
Thanks,
Yunze
> On Sep 6, 2022, at 11:56, Yu wrote:
>
> Hi Yunze,
>
> Thanks for updating the workflow!
>
> ~~
>
> Hi all,
>
> For the release process, we've updated the doc-related workflow [1] since
> we changed the doc maintenance strategy [2]
Hi Yunze,
Thanks for updating the workflow!
~~
Hi all,
For the release process, we've updated the doc-related workflow [1] since
we changed the doc maintenance strategy [2].
TL;DR
Breaking change:
For release managers: from 2.8.x, you do not need to generate
an independent doc set for
