https://bugzilla.redhat.com/show_bug.cgi?id=1564115
Bug ID: 1564115
Summary: need option 'run brick-mux-tests' in reviews
Product: GlusterFS
Version: mainline
Component: project-infrastructure
Severity: high
Assignee: b...@g
https://bugzilla.redhat.com/show_bug.cgi?id=1563379
Nigel Babu changed:
What|Removed |Added
CC||nig...@redhat.com
--- Comment #1 from Ni
https://bugzilla.redhat.com/show_bug.cgi?id=1564130
Bug ID: 1564130
Summary: need option 'cherry-pick to release-x.y' in reviews
Product: GlusterFS
Version: mainline
Component: project-infrastructure
Severity: high
Assignee:
https://bugzilla.redhat.com/show_bug.cgi?id=1564139
Bug ID: 1564139
Summary: need a test to validate flags and validity of github
issues.
Product: GlusterFS
Version: mainline
Component: project-infrastructure
Sever
https://bugzilla.redhat.com/show_bug.cgi?id=1564115
--- Comment #1 from Niels de Vos ---
We now have a "Verified" label in Gerrit. I think it should be possible to add
an other label "Test w/ brick-mux' or similar that triggers this special test.
It will be used more than when a magic comment i
https://bugzilla.redhat.com/show_bug.cgi?id=1563379
Kaleb KEITHLEY changed:
What|Removed |Added
Keywords||Triaged
Assignee|b...@gluste
https://bugzilla.redhat.com/show_bug.cgi?id=1564149
Bug ID: 1564149
Summary: Agree upon a coding standard, and automate check for
this in smoke
Product: GlusterFS
Version: mainline
Component: project-infrastructure
https://bugzilla.redhat.com/show_bug.cgi?id=1564115
--- Comment #2 from Amar Tumballi ---
I personally feel lesser tick-boxes, but more commands, and documenting them.
It would get closer to github flow, so it will reduce the overall dependency to
understand gerrit for someone who comes from gi
https://bugzilla.redhat.com/show_bug.cgi?id=1564149
--- Comment #1 from Jeff Darcy ---
If we're going to make a big-bang format change, I'd like to propose that we
also move toward shorter indentation. The standard at Facebook is two spaces,
which my old eyes consider too narrow, but eight is u
https://bugzilla.redhat.com/show_bug.cgi?id=1564149
--- Comment #2 from Amar Tumballi ---
How about keeping tabs, and making the 80line check on 4space for tab config?
Also provide relevant vim and emacs config to people (may be in extras).
--
You are receiving this mail because:
You are on t
https://bugzilla.redhat.com/show_bug.cgi?id=1564149
Xavi Hernandez changed:
What|Removed |Added
CC||jaher...@redhat.com
--- Comment #3 f
https://bugzilla.redhat.com/show_bug.cgi?id=1564149
--- Comment #4 from Shyamsundar ---
Overall ack to the proposal.
Nice call-out by Jeff on any other change requiring a big-bang addressing to be
a part of the same.
I can live with 4 spaces :), but no tabs (way too much discrepancy across
ed
https://bugzilla.redhat.com/show_bug.cgi?id=1564149
--- Comment #5 from Jeff Darcy ---
I think we're all in agreement on spaces vs. tabs. Tabs are eight spaces wide,
full stop, end of story. It's kind of survivable with eight-space indents, but
any other indent width becomes a total nightmare i
https://bugzilla.redhat.com/show_bug.cgi?id=1564115
Nigel Babu changed:
What|Removed |Added
CC||nig...@redhat.com
--- Comment #3 from Ni
https://bugzilla.redhat.com/show_bug.cgi?id=1564139
Nigel Babu changed:
What|Removed |Added
CC||nig...@redhat.com
--- Comment #1 from Ni
https://bugzilla.redhat.com/show_bug.cgi?id=1564115
--- Comment #4 from Amar Tumballi ---
No serious need of 'Vote' at present. This can be 'SUCCESS', 'FAILURE', ABORT
or whatever.. as the person triggering the run, I would look up the result
before voting.
Lets get the basic trigger infra to
https://bugzilla.redhat.com/show_bug.cgi?id=1564372
Bug ID: 1564372
Summary: Setup Nagios server
Product: GlusterFS
Version: 4.0
Component: project-infrastructure
Assignee: b...@gluster.org
Reporter: nig...@redhat.com
17 matches
Mail list logo
