[NOTICE] Please submit the code to the INLONG-739 branch

[Goson zhang <go...@apache.org>]

The 0.9.0 is being released, during the release period, the version may be
returned to the reissued version. In order to facilitate the
synchronization of version release and development, I created a branch
version [INLONG-739] for the next version iteration.

This version is not the initial version, and will retain the submission
details of each PR. Everyone submits the code to be adjusted in accordance
with the specifications, and the verification is passed and then
incorporated.

After the 0.9.0 version is released, we will merge the content of the
INLONG-739 branch into the master and resume the master submission.

Thanks!

Re: [NOTICE] Please submit the code to the INLONG-739 branch

[Goson zhang <go...@apache.org>]

Someone mentioned a more professional and general approach: all the
modifications during the release period are merged into the Master

The reason is that: we have released a version and have established a
version branch, for example, the branch of 0.9.0 is release-0.9.0, if it is
a version problem, we can modify it directly in the version branch and
after the modification is completed, it will be merged into the Master;
follow-up collaboration When there are many people, it is very common to
pull a new branch to make a big feature, and it needs a mainline-based
operation instead of temporarily pulling a branch and letting everyone
remember this temporary branch.

I think it makes sense, do you have any other opinions? If not, let's use
Master as the development branch for the next version, pull the branch
separately, and merge the changes back to the mainline after the version is
released.

Thank you

Goson zhang <go...@apache.org> 于2021年7月13日周二 下午1:13写道：

> The 0.9.0 is being released, during the release period, the version may be
> returned to the reissued version. In order to facilitate the
> synchronization of version release and development, I created a branch
> version [INLONG-739] for the next version iteration.
>
> This version is not the initial version, and will retain the submission
> details of each PR. Everyone submits the code to be adjusted in accordance
> with the specifications, and the verification is passed and then
> incorporated.
>
> After the 0.9.0 version is released, we will merge the content of the
> INLONG-739 branch into the master and resume the master submission.
>
> Thanks!
>