[Gluster-infra] [Bug 1428034] Enable gerrit to convert github issue reference as a hyperlink
https://bugzilla.redhat.com/show_bug.cgi?id=1428034 --- Comment #6 from Shyamsundar --- (In reply to Nigel Babu from comment #5) > Shyam, take a look at this when you get some time -> > https://review.gluster.org/#/c/16901/ (It's a draft and you're CC'd. Need to > be logged in to see) Checked the above and here are some questions: 1) We want the commit message to read "Fixes: #n" OR "Fixes: gluster/glusterfs#n" OR "Updates: #n" OR "Updates: gluster/gusterfs#n". Will the link substitution work for all of the above? 2) When a repo name is not mentioned in the commit message when referencing an issue # (for example: "Updates: #n") the default is gluster/glusterfs is the thought. I understand that later, some other repositories that end up using the same scheme, will have trouble if so, but we want this as the default for the glusterfs repo, so this is a repo specific default, IOW, a commit against repo with no repo reference in the issue #, automatically becomes a link to an issue against that repo 3) Just stating, we will not reference any issue in gluster-specs, we will submit patches to specs that refer to issues in glusterfs repo, like "Updates: gluster/glusterfs#n" 4) I think we should also enforce (if this is the right layer to do it), that either a Fixes/Updates keyword is present before the issue reference. -- 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=yxvG25S8te&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1431969] pull gluster-block v0.1-2 into d.g.o
https://bugzilla.redhat.com/show_bug.cgi?id=1431969 Nigel Babu changed: What|Removed |Added Status|ASSIGNED|CLOSED Resolution|--- |CURRENTRELEASE Last Closed||2017-03-15 06:01:34 --- Comment #8 from Nigel Babu --- This is now sorted: https://download.gluster.org/pub/gluster/gluster-block/ I've also setup this repo file: https://download.gluster.org/pub/gluster/gluster-block/gluster-block.repo If users have that installed, they can download be on the latest version as we release 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=mhCurY3ZWs&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1431969] pull gluster-block v0.1-2 into d.g.o
https://bugzilla.redhat.com/show_bug.cgi?id=1431969 --- Comment #7 from Prasanna Kumar Kalever --- +1 Nigel. I am okay this way either. -- 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=B0RMQdwcKp&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1431969] pull gluster-block v0.1-2 into d.g.o
https://bugzilla.redhat.com/show_bug.cgi?id=1431969 --- Comment #6 from Nigel Babu --- Different directories makes it cleaner to download the latest package and also use the older packages. Wouldn't that be less confusing? My knowledge around rpm repos aren't perfect, so happy to be proven wrong here. -- 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=HD0vyX4nPD&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1431969] pull gluster-block v0.1-2 into d.g.o
https://bugzilla.redhat.com/show_bug.cgi?id=1431969 Anoop C S changed: What|Removed |Added CC||anoo...@redhat.com --- Comment #5 from Anoop C S --- (In reply to Prasanna Kumar Kalever from comment #4) > So if you see the package name here [1] it is gluster-block-0.1-1.x86_64.rpm > > The new package name will be gluster-block-0.1-2.x86_64.rpm > > So ideally, the new path should be > https://download.gluster.org/pub/gluster/gluster-block/0.1-2/ Why should this be under different directory? I would say we put new rpms under 0.1 directory itself i.e, https://download.gluster.org/pub/gluster/gluster-block/0.1/fedora/25/x86_64/ > > > Thoughts ? > > > [1] > https://download.gluster.org/pub/gluster/gluster-block/0.1/fedora/25/x86_64/ -- 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=leCJfV3KLP&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1431969] pull gluster-block v0.1-2 into d.g.o
https://bugzilla.redhat.com/show_bug.cgi?id=1431969 Prasanna Kumar Kalever changed: What|Removed |Added Flags|needinfo?(prasanna.kalever@ | |redhat.com) | --- Comment #4 from Prasanna Kumar Kalever --- So if you see the package name here [1] it is gluster-block-0.1-1.x86_64.rpm The new package name will be gluster-block-0.1-2.x86_64.rpm So ideally, the new path should be https://download.gluster.org/pub/gluster/gluster-block/0.1-2/ Thoughts ? [1] https://download.gluster.org/pub/gluster/gluster-block/0.1/fedora/25/x86_64/ -- 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=DolMJ5aGaE&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1431969] pull gluster-block v0.1-2 into d.g.o
https://bugzilla.redhat.com/show_bug.cgi?id=1431969 Nigel Babu changed: What|Removed |Added Flags||needinfo?(prasanna.kalever@ ||redhat.com) --- Comment #3 from Nigel Babu --- okay so we currently have: https://download.gluster.org/pub/gluster/gluster-block/0.1/ The new release will be: https://download.gluster.org/pub/gluster/gluster-block/0.1-2/ Would it make sense instead to do 0.1.1 instead? This way you can use the dashed numbers as numbers for the build in case there are build failures on your first attempt. Happy to go with 0.1-2 as well. Let me know which works best. -- 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=kuItcHsSxW&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-infra
