Alright, it seems like I need to read what the script actually does.
Although I haven't read the script at all, I don't understand how we can
automate something without policies, rules, whatever. I guess the script does
the task based on something. It is expecting something. I think the something
is apart of policies ("policy" and "rule" are different but I used it as
"something we should follow").
And I guess the script ease the pain you stated in your motivation below.
> Labels and milestones are not marked correctly. Changes are not cherry-picked
> to branches.
It causes a lot of troubles for release managers to do a release.
These are why I though some policy is coded into the script.
Anyways, I hope our comments here made people think about policies.
As for ways of doing things, I agree. How things can be done depends on people
in the community. I was suggesting that automating is not the only way. Because
I believe steps are based on some policy, I think people can do some of the
things without enforcing with scripts once we define clear policies.
As for the pain points, my point is that showing what you exactly saw during
releases and explaining how labels, milestones, etc help RM is more effective
than just saying missing things cause problems.
[ Full content available at:
https://github.com/apache/incubator-pulsar/pull/2526 ]
This message was relayed via gitbox.apache.org for [email protected]
