Skip to content
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

rohitsardesai83
Copy link
Collaborator

Cherry pick of #493 on release-0.3.

#493: Refactor the code to remove redundant statements

Signed-off-by: Dave Chen <dave.chen@arm.com>
@m1093782566
Copy link

Is this a bug fix or usage guide? If not, I would suggest move it to v1.0.

@rohitsardesai83
Copy link
Collaborator Author

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

@sids-b
Copy link
Member

sids-b commented May 28, 2019

@m1093782566 , it is just removal of redundant code.

@sids-b
Copy link
Member

sids-b commented May 28, 2019

/lgtm

@kubeedge-bot kubeedge-bot added the lgtm Indicates that a PR is ready to be merged. label May 28, 2019
@m1093782566
Copy link

m1093782566 commented May 28, 2019

@rohitsardesai83 @sids-b

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.

cc @kevin-wangzefeng

@sids-b
Copy link
Member

sids-b commented May 28, 2019

Actually it is code cleanup of the feature(deviceController) which was introduced in v0.3.0-beta.0.

@rohitsardesai83
Copy link
Collaborator Author

@rohitsardesai83 @sids-b

I think you may misunderstand the criteria of cherry-pick. I think only bug fixes worth cherry-picking to a specific release branch - you may refer to Kubernetes.

cc @kevin-wangzefeng

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.

@sids-b
Copy link
Member

sids-b commented May 28, 2019

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 ?
Thoughts @kevin-wangzefeng @m1093782566 ?

@m1093782566
Copy link

it is a cleanup activity which I think should be ok to be cherry picked.

I think we need to set some barries for cherry-picks for decreasing the number of cherry-picks. Thoughts?

@m1093782566
Copy link

So i feel adding code cleanups , docs and CRD examples should be fine ?

Do you mean all?

@kevin-wangzefeng
Copy link
Member

kevin-wangzefeng commented May 28, 2019

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.

@rohitsardesai83 rohitsardesai83 deleted the automated-cherry-pick-of-#493-upstream-release-0.3 branch June 26, 2019 10:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants