[Gluster-infra] Priorities on recently filed infrastructure issues (by me)
Hi, My apologies, I just filed 4 issues against infra and did not call out what is needed and by when, so here goes, (Prio. 1 does not mean I needed it yesterday, just a relative priority among these). Prio. 1) https://bugzilla.redhat.com/show_bug.cgi?id=1428032 Update WorkerAnt to post to a github issue as soon as a patch is posted against the same Prio. 1) https://bugzilla.redhat.com/show_bug.cgi?id=1428034 Enable gerrit to convert github issue reference as a hyperlink The above 2 are P1's as we need this information flowing for 3.11 Prio. 2) https://bugzilla.redhat.com/show_bug.cgi?id=1428036 Update rfc.sh to check/request issue # when a commit is an “rfc” NOTE: This is out of infra anyway, as this is part of the code base, so no longer an infra priority Prio. 5) https://bugzilla.redhat.com/show_bug.cgi?id=1428047 Require a Jenkins job to validate Change-ID on commits to branches in glusterfs repository NOTE: This is still under discussion and NEEDINFO on me, but just noting it here for completeness The above is P5 as we can live without it (as we have been till now) for some more time. Thanks, Shyam ___ Gluster-infra mailing list Gluster-infra@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1428034] Enable gerrit to convert github issue reference as a hyperlink
https://bugzilla.redhat.com/show_bug.cgi?id=1428034 --- Comment #4 from Shyamsundar --- (In reply to Niels de Vos from comment #3) > Because we now get into a mix of numbers pointing to either Bugzilla or > GitHub, I suggest to have the "BUG: 012345" replaced by URLs. The same We do not get a mix of numbers, we get BUG:12345 as BZ link, and get Fixes #n or Updates #n (or Fixes gluster/glusterfs#n or Updates gluster/glusterfs#12) as github links. This maybe an example of the same (as Nigel is playing with it), https://gerrit-stage.rht.gluster.org/#/c/16405/8 > approach needs to be done for GitHub issues. For someone reading the commit > messages, a single well known source for bug reports and RFEs is easy, when > we have two it will become confusing for many. Agreed, this is elegant, BUT I want this functionally ready soon, and optimized later. If both can be done at the same time by Nigel, or the approach that you suggest is the one we take now or in the future, I leave to Nigel. What is currently (being) done by Nigel is sufficient to get started and take to collaborators out there, and hence I would not like to delay that. -- 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=XGsqlx4zFt&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1428032] Update WorkerAnt to post to a github issue as soon as a patch is posted against the same
https://bugzilla.redhat.com/show_bug.cgi?id=1428032 --- Comment #4 from Shyamsundar --- (In reply to Nigel Babu from comment #1) > glusterfs/glusterfs-specs are the only repos that will have any work done. Yes, agreed, glusterdocs is not via gerrit, and github will take care of the mention for us. > The problem here is to remove duplication. We currently push to bugzilla > every time a patchset is created. For features there will be no bug in the commit message, it will be of the rfc type, so if I read your comment here right, WorkerAnt will automagically hence post to Bugzilla or to github only and not to both, right? So the duplication problem does not exist? (or are you referring to the duplication issue as discussed in the next para by you, in which case, disregard this comment) > > For a large change, there may be multiple pushes that will create noise if > we add comment on every patchset. This needs to be fixed for Bugzilla *as > well*. Once that's sorted, we'll make the change for Github. Sigh! yes this is true and to some extent I agree that it is noise as well (hence the sigh). At the same time this repetitive posting also (sometimes) helps (maybe), that there is a new change that you may want to look at when following the bug (or in this case the issue). > > Does this sound acceptable? I would like to treat the noise and posting to github issues separately, as I would like the github issue posting to appear sooner, but that assumes I know how much effort it would take to do both. Does this answer your question on acceptability. I will also send in a mail with the various requests that have been made of the infra team with some form of priority to them, just so we are on the same page. (apologies if this is causing confusion at present) > > glusterdocs is handled entirely in Github. If you mention an issue in the > pull request, it will do the linking already. Yes, agreed. -- 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=FXeQrUwkWw&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1428036] Update rfc.sh to check/ request issue # when a commit is an “rfc”
https://bugzilla.redhat.com/show_bug.cgi?id=1428036 Shyamsundar changed: What|Removed |Added Component|project-infrastructure |unclassified --- Comment #2 from Shyamsundar --- (In reply to Nigel Babu from comment #1) > This need not be an infra bug. This can be handled in the Gluster code base > by modifying rfc.sh yourself. For git-review, you could write a pre-review > hook that's shipping with glusterfs-specs that need to be copied to the > hooks folder. Thoughts? Yes, agree. Changing the component appropriately (which unfortunately goes to unclassified). -- 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=zACx1khIfz&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1413953] gerrit session expires frequently
https://bugzilla.redhat.com/show_bug.cgi?id=1413953 --- Comment #3 from Nigel Babu --- Does this only happen when you open multiple new tabs? -- 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=xE5f6r76sn&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1424982] Need a new project to be hosted on gerrit for gluster-block
https://bugzilla.redhat.com/show_bug.cgi?id=1424982 Nigel Babu changed: What|Removed |Added Status|ASSIGNED|CLOSED Resolution|--- |CURRENTRELEASE Last Closed|2017-02-20 21:42:08 |2017-03-03 05:56:57 --- Comment #9 from Nigel Babu --- Haven't heard anything back. Closing. -- 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=JjHTs8yCpi&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1426165] need a NETBSD machine to debug tier bad tests
https://bugzilla.redhat.com/show_bug.cgi?id=1426165 Nithya Balachandran changed: What|Removed |Added CC||nbala...@redhat.com --- Comment #2 from Nithya Balachandran --- Created attachment 1259440 --> https://bugzilla.redhat.com/attachment.cgi?id=1259440&action=edit Nithya's public key -- 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=h7MbjzeNUA&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1360173] Cherry-picking changes to release branches via Gerrit Web UI wrongly sets the 'Topic' field
https://bugzilla.redhat.com/show_bug.cgi?id=1360173 Nigel Babu changed: What|Removed |Added Status|NEW |CLOSED Resolution|--- |WONTFIX Last Closed||2017-03-03 03:57:33 --- Comment #1 from Nigel Babu --- I've gone looking for this. Turns out, this is an intentional change in Gerrit UI. See: https://gerrit-review.googlesource.com/#/c/66440/ Marking as WONTFIX. -- 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=XsFeoJBiCb&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-infra
