Were these guidelines voted and agreed upon by the community?
Thanks the question Arpit.
Unfortunately I am not sure If I understand it well.
1. Based on direct meaning you are asking about where the Ozone VOTEs
can be found.
They are always part of the mailing list traffic and archive can be
found on https://lists.apache.org/
There was no VOTE related to how merging any branches.
2. As I am almost sure that you know it, it can be a suggestion, but I
would like to ask to clarify it.
As far as I see merges are voted by individuals and we couldn't VOTE on
binding rules how the votes should be cast.
But let me know if you have some suggestions.
The checklist is discussed on the community sync and a mail also sent to
the mailing list. Based on the feedback it can be helpful. It seems that
we all interested about maintaining the stability. I think identifying
possible problems can help us to avoid them in advance.
The only one risk what I see that the merge would be delayed with
significant time due to the stabilization/documentation work. To avoid
it here I offer my help and full support to keep both agility and
stability. Especially about the build and containerization related
stuff, but also happy to write down documentation if somebody can help
with explaining a few questions.
Also happy to test it in containerized environment. Until now it helped
a lot as different deployment model helped us to find different
problems, but which were _generic_ to any of the deployment model.
Thanks,
Marton
On Tue, Mar 9, 2021, 4:20 AM Elek, Marton <e...@apache.org
<mailto:e...@apache.org>> wrote:
Thanks to start the discussion Shashikant,
Good to see that SCM HA is close to the merge.
I like Attila's suggestion:
+1 to check stability based on the checklist and create a wiki page.
And +1 the merge after we have passed all the items (as we will have
enough information to believe that master stability will be fine).
Marton
On 3/9/21 11:30 AM, Attila Doroszlai wrote:
Thanks Shashikant for starting the discussion.
Marton has recently proposed a solid checklist to go through before
branch merge:
https://cwiki.apache.org/confluence/display/OZONE/Merging+branches
<https://cwiki.apache.org/confluence/display/OZONE/Merging+branches>
One of the items is basic documentation as suggested by Xiaoyu.
It would be great if we could get a clear status of the SCM HA branch
by going through the checklist and providing answers/information about
each point (where applicable). I suggest writing it up as a wiki
page: various items may be addressed by different people, plus if some
area needs improvement, we could track the changes without spamming
the list.
thanks,
Attila
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org
<mailto:dev-unsubscr...@ozone.apache.org>
For additional commands, e-mail: dev-h...@ozone.apache.org
<mailto:dev-h...@ozone.apache.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org
<mailto:dev-unsubscr...@ozone.apache.org>
For additional commands, e-mail: dev-h...@ozone.apache.org
<mailto:dev-h...@ozone.apache.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org
For additional commands, e-mail: dev-h...@ozone.apache.org
