On 2014-07-09 15:02, Niels de Vos wrote: > On Tue, Jul 08, 2014 at 11:40:35AM +0100, Justin Clift wrote: >> On 08/07/2014, at 9:53 AM, Anders Blomdell wrote: >> <snip> >>> 2. What are the rules for marking a bug as blocking the trackers (can't find one for >>> 3.6.0 yet, so currently a moot point). >> >> We should probably create an alias thing for 3.6.0, like we >> have for 3.5.2: >> >> https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.5.2 >> >> Not sure who does that, maybe Vijay (CC'd)? > > Anyone can do that, I've now created one for 3.6.0: > - https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.6.0 Thanks :-) > > When there are urgent bugs that need to get fixed in 3.6.0, open the bug > (not the tracker) and add 'glusterfs-3.6.0' (or 1117822) in the 'blocks' > field. If that is not working due to some permission issues, send an > email to this list or ask on Freenode/IRC in #gluster-dev if someone can > take care of adding it to the tracker. Have added my own favorite itches to it. I still don't feel confident enough with git to add my patches to gerrit and get jenkins to do the right thing is probably even worse, so where I have code that works for me™, bug reports contains patches, please bear with me. Removal of erroneous blockers should preferably be done without flame-throwers :-) BTW: doc/hacker-guide/en-US/markdown/unittest.md seems to lack info on how to write tests/bugs/bug-*.t files. /Anders -- Anders Blomdell Email: anders.blomdell@xxxxxxxxxxxxxx Department of Automatic Control Lund University Phone: +46 46 222 4625 P.O. Box 118 Fax: +46 46 138118 SE-221 00 Lund, Sweden _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-devel