-
Notifications
You must be signed in to change notification settings - Fork 554
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
merge csiv1.0 branch to master #297
Conversation
Signed-off-by: Peter Nordquist <peter.nordquist@pnnl.gov>
Signed-off-by: Huamin Chen <hchen@redhat.com>
Signed-off-by: Huamin Chen <hchen@redhat.com>
…not hosted in quay.io Signed-off-by: Huamin Chen <hchen@redhat.com>
Merge master to csi-v1.0 branch
Signed-off-by: Madhu Rajanna <mrajanna@redhat.com>
Signed-off-by: Madhu Rajanna <mrajanna@redhat.com>
Signed-off-by: Madhu Rajanna <mrajanna@redhat.com>
Signed-off-by: Madhu Rajanna <mrajanna@redhat.com>
Signed-off-by: Madhu Rajanna <mrajanna@redhat.com>
Signed-off-by: Madhu Rajanna <mrajanna@redhat.com>
Signed-off-by: Madhu Rajanna <mrajanna@redhat.com>
Csi v1.0 cleanup
…ock volume provisioning Signed-off-by: Huamin Chen <hchen@redhat.com>
Signed-off-by: Huamin Chen <hchen@redhat.com>
support block volume
…n get latest mons and override old ones Signed-off-by: Huamin Chen <hchen@redhat.com>
update travis.yaml and deploy.sh to build v0.3.0 images from csi-v0.3 branch instead of master. Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
…n-exit-v2 remount old mount point when csi plugin unexpect exit
update travis.yml and deploy.sh
@rootfs @ShyamsundarR @gman0 @j-griffith @humblec PTAL, This PR makes csiv1.0 branch as master with preserving git history from csiv1.0 branch |
updates issue #266 |
@Madhu-1 will be on this soon. |
An clarification question, instead of the merge can we not delete and rename csi-v1.0 branch as the master? Or, do we intend to leave the csi-v1.0 branch as is and never delete that branch? |
@ShyamsundarR I thought of doing only if I face any issue in merging csi-v1.0 into master and also I felt deleting a branch is kind of risky for me. so the current plan is to merge the csi-v1.0 changes to the master and delete csi-v1.0 branch(make master as the default branch) any comments on this approach? |
One option would be, branchoff from current Any thoughts @gman0 @ShyamsundarR @j-griffith @Madhu-1 ? |
whats the intention of keeping v1.0 branch? are we going to merge PR to csiv1.0 branch and do a release from it? if we come to an agreement soon enough so that we can have a master branch with v1.0.0. |
Just checked a branch diff between this PR and csi-v1.0 branch it is clean. I would vote to not prolong this, by taking other alternatives (like delete/rename), as the bulk of the work is done. I cannot say if commits will bisect well or not (I think our merge strategy also defeats the bisection unless PR owners ensure their commits are bisect-able (individually work)). I was more curious as to why this option/route was taken to ensure we have master caught up with the current 1.0 branch. BUT, I do want to discuss what we do with csi-v1.0 branch post this merge, IMO,
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work @Madhu-1
lgtm. |
merge csiv1.0 branch to master
Syncing latest changes from upstream devel for ceph-csi
No description provided.