-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automated cherry pick of #493: Refactor the code to remove redundant statements #588
Conversation
Signed-off-by: Dave Chen <dave.chen@arm.com>
Is this a bug fix or usage guide? If not, I would suggest move it to v1.0. |
This is a code improvement needed for v0.3 |
@m1093782566 , it is just removal of redundant code. |
/lgtm |
I think you may misunderstand the criteria of cherry-pick. I think only bug fixes worth cherry-picking to a specific release branch - you can see Kubernetes for reference. If the code refactor is necessary for later cherry-picks, I can let it in but for now I don't see any. |
Actually it is code cleanup of the feature(deviceController) which was introduced in v0.3.0-beta.0. |
since the device controller was introduced as a part of 0.3 release , and this code doesn't introduce any new feature , it is a cleanup activity which I think should be ok to be cherry picked. Only thing is this activity was not associated with any issue. We should in such cases follow practice of always opening issues and then raise PRs. |
And also we are cherry picking for 0.3.0 which is a minor release and not a patch release. So i feel adding code cleanups , docs and CRD examples should be fine ? |
I think we need to set some barries for cherry-picks for decreasing the number of cherry-picks. Thoughts? |
Do you mean all? |
The release-xx branches only accepts imporntant bugfixes and document updates. New features, refactoring, clean-up, or fixes that changing functionalities behaviour should not be accepted. |
Cherry pick of #493 on release-0.3.
#493: Refactor the code to remove redundant statements