Thanks the answer Aravindan.
If large scale changes
are expected after the VOTE, I believe as project PMC/committers we would
let the dev know. I am sure we are not trying to get approval for 'A', and
then merge 'B'.
Just let me clarify it: I am not concerned about large changes after
VOTE. We already discussed the design and we had a strong agreement.
I am concerned about the small issues which can be fixed easily. But
here, the power of the community can help: with the following two inputs
everybody can help to do a final test:
* at least a basic documentation (we have it)
* A commit proposed to be merged (to make it possible to compare the
results)
This is very similar to what we do for each release. Just do a final
smoke check to be sure we are fine.
And similar to a release, one small commit can be a big difference (a
wrong LICENSE can be a release blocker, or one very unstable test can be
a merge blocker ).
That's the reason why I asked for a commit hash: a well-specified plan
to vote on. (but as far as I remember I was not the only one...)
Thanks again the answer and the great work,
Marton
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org
For additional commands, e-mail: dev-h...@ozone.apache.org
