...and I'm sorry about that, the following documents are somewhat contradictory:
http://gluster.org/community/documentation/index.php/Simplified_dev_workflow
The script will ask you to enter a bugzilla bug id. Every
change submitted to GlusterFS needs a bugzilla entry to be
accepted. If you
I don't understand your confusion, but maybe these docs need to be reworded.
What both of these want to say is that for a patch to be merged into
glusterfs, it needs to be associated with a bug-id. This association
is done by adding a 'BUG: id' line in the commit message. If you
haven't manually
On 2014-07-17 15:44, Kaushal M wrote:
I don't understand your confusion, but maybe these docs need to be reworded.
Not confused, just observed that some of my patches regarding development
workflow does not need to show up as bugs for gluster (at least not until
somebody has verified that they
Bugs/bug in the documents are not really what you think they mean.
We use bugzilla to track glusterfs development. It is used for track
defects (bugs) in the software, enhancements and new features. What we
really mean by a patch needs a bug id is that we need it to have an
entry on bugzilla, so
