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

[bug:1629877] GlusterFS can be improved (clone for Gluster-5) #1001

Closed
gluster-ant opened this issue Mar 12, 2020 · 6 comments
Closed

[bug:1629877] GlusterFS can be improved (clone for Gluster-5) #1001

gluster-ant opened this issue Mar 12, 2020 · 6 comments

Comments

@gluster-ant
Copy link
Collaborator

URL: https://bugzilla.redhat.com/1629877
Creator: srangana at redhat
Time: 20180917T14:39:57

+++ This bug was initially created as a clone of Bug #1193929 +++

I hope this bug is never fixed.

The upstream patch process requires that each patch have an associated bug ID before it can be merged. However, there is no requirement that the bug contain any information or receive any kind of signoff before the patch can proceed. As a result, many of our developers have the habit of creating such "placeholder" bugs every time they want to make a change, even if it's just a random cleanup/idea and not an actual bug fix or requested/tracked feature request. Also, any patch with the dreaded "rfc" bug ID (which would be appropriate for such changes) is unlikely to be reviewed.

This bug exists to satisfy our process requirement, without the additional negatives of clogging up our triage/tracking processes and making it appear that the code has more bugs (which would be bad) when in fact a developer had more ideas (which is generally good).

@gluster-ant
Copy link
Collaborator Author

Time: 20180917T14:44:10
bugzilla-bot at gluster.org commented:
REVIEW: https://review.gluster.org/21195 (gfapi: Cleanup alias file) posted (#1) for review on release-5 by Shyamsundar Ranganathan

@gluster-ant
Copy link
Collaborator Author

Time: 20180917T19:30:20
bugzilla-bot at gluster.org commented:
COMMIT: https://review.gluster.org/21195 committed in release-5 by "Shyamsundar Ranganathan" srangana@redhat.com with a commit message- gfapi: Cleanup alias file

2 extra symbols were in the alias file, that are not exported
this is cleaned up with this patch.

Change-Id: I1ab54b9fb6b0d455884fbbfd89820c60bb861e6f
Updates: bz#1629877
Signed-off-by: ShyamsundarR srangana@redhat.com

@gluster-ant
Copy link
Collaborator Author

Time: 20181023T15:19:00
srangana at redhat commented:
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-5.0, please open a new bug report.

glusterfs-5.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://lists.gluster.org/pipermail/announce/2018-October/000115.html
[2] https://www.gluster.org/pipermail/gluster-users/

@gluster-ant
Copy link
Collaborator Author

Time: 20190612T06:33:48
bugzilla-bot at gluster.org commented:
REVIEW: https://review.gluster.org/22855 (tests/utils: Fix py2/py3 util python scripts) posted (#1) for review on release-5 by hari gowtham

@gluster-ant
Copy link
Collaborator Author

Time: 20190701T07:02:25
bugzilla-bot at gluster.org commented:
REVIEW: https://review.gluster.org/22855 (tests/utils: Fix py2/py3 util python scripts) merged (#3) on release-5 by hari gowtham

@rkothiya
Copy link

rkothiya commented Oct 7, 2020

As discussed and agreed in the team meeting, we will be using the existing bug link pasted below to track any improvements hence closing this bug.
#1000

@rkothiya rkothiya closed this as completed Oct 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants