[Gluster-infra] [Bug 1564149] Agree upon a coding standard, and automate check for this in smoke

2018-04-06 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1564149

Shreyas Siravara  changed:

   What|Removed |Added

 CC||sshre...@fb.com



--- Comment #6 from Shreyas Siravara  ---
Whoever came up with this idea is a genius, and I totally ack it :)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=2quGLHK1M0&a=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1564451] New: The abandon job for patches should post info in bugzilla that some patch is abandon 'd.

2018-04-06 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1564451

Bug ID: 1564451
   Summary: The abandon job for patches should post info in
bugzilla that some patch is abandon'd.
   Product: GlusterFS
   Version: mainline
 Component: project-infrastructure
  Severity: high
  Assignee: b...@gluster.org
  Reporter: atumb...@redhat.com
CC: amukh...@redhat.com, b...@gluster.org,
gluster-infra@gluster.org, j...@pl.atyp.us,
srang...@redhat.com



# Description of problem:

Today there are many users who just report bug, and not followup much in gerrit
for the fix. When the fix is posted, the bug gets updated, and automatically
transitioned. But assuming it gets abandon'd due to inactivity or something
else, bugzilla users won't even have a clue. So, it would be good to leave a
note in bugzilla that patch is now abandon'd. So relevant people may take
actions.

# Additional info:

I am not sure if it should bother to transition back the status to ASSIGNED/NEW
in that case. Lets keep that one for later. For now, just a update in bugzilla
is good enough, saying "The patch  is abandon'd due to inactivity" (not
sure we can capture abandon click from browser as a event, even in that case,
it should be noted in bugzilla.

Again, for now, not expecting github post for this. We will get to it later.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=Q2QTxHe4pW&a=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1564139] need a test to validate flags and validity of github issues.

2018-04-06 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1564139



--- Comment #2 from Amar Tumballi  ---
The note to community was that we are willing to make edits to behavior on
discussion, and will go ahead and implement soon for making sure we have
documentation for the features. Can we start this from April 15th?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=wFwNlNigfH&a=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-infra