<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 21 Feb 2017, at 09:36, Eyal Edri <<a href="mailto:eedri@redhat.com" class="">eedri@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><br class=""><div class="gmail_extra"><br class=""><div class="gmail_quote">On Tue, Feb 21, 2017 at 10:34 AM, Sandro Bonazzola <span dir="ltr" class=""><<a href="mailto:sbonazzo@redhat.com" target="_blank" class="">sbonazzo@redhat.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class=""><br class=""><div class="gmail_extra"><br class=""><div class="gmail_quote"><span class="">On Tue, Feb 21, 2017 at 9:31 AM, Eyal Edri <span dir="ltr" class=""><<a href="mailto:eedri@redhat.com" target="_blank" class="">eedri@redhat.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class=""><br class=""><div class="gmail_extra"><br class=""><div class="gmail_quote"><span class="">On Tue, Feb 21, 2017 at 10:20 AM, Sandro Bonazzola <span dir="ltr" class=""><<a href="mailto:sbonazzo@redhat.com" target="_blank" class="">sbonazzo@redhat.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="">Hi,<div class="">I'm facing a new challenge today, I see new features getting pushed to oVirt gerrit intentionally out of bugzilla.</div><div class="">The specific case is not really relevant, but just for reference: <a href="https://gerrit.ovirt.org/#/c/65761/" target="_blank" class="">https://gerrit.ovir<wbr class="">t.org/#/c/65761/</a> .</div><div class="">Looks like we'll see features getting merged without any RFE opened in bugzilla for them.</div></div></blockquote></span></div></div></div></blockquote></span></div></div></div></blockquote></div></div></div></div></blockquote><div><br class=""></div>this is a common case for master, many patches do not have Bug-Url including features initially</div><div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class=""><div class="">With current workflow, auto-generating release notes from bugzilla doc-texts. this means they won't ever be documented.</div></div></blockquote></span></div></div></div></blockquote></span></div></div></div></blockquote></div></div></div></div></blockquote><div><br class=""></div>true. Typically they don’t have to be as for user consumable features there is typically many patches, and eventually the final part of feature do have proper tracking, RFE and so on.</div><div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class=""><div class=""><br class=""></div><div class="">I'd like to open this public discussion getting comments about how things will be handled.</div></div></blockquote><div class=""><br class=""></div></span><div class="">We can start enforcing bug-url in master branch as well, maybe under certain conditions. </div></div></div></div></blockquote></span></div></div></div></blockquote></div></div></div></div></blockquote><div><br class=""></div>I do not see the current practice as problematic</div><div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><span class=""><div class=""><br class=""></div></span><div class="">The issue here is that the decision is to not use bugzilla and use something different like trello.</div><div class="">So enforcing bug-url will collide with the decision from the feature owner team.</div></div></div></div></blockquote><div class=""><br class=""></div><div class="">If there is an official decision ( I havn't heard on such ) to move to another issue tracker for some of the projects then it needs to be planned,</div></div></div></div></div></blockquote><div><br class=""></div>Some of the projects decided not to use bugzilla. It’s a project decision, not an “official” decision affecting other projects.</div><div>In this case the reason is that a supposed feature triggered a code change in a side project using bugzilla. </div><div>I would say in that case it either deserves a bugzilla on that side project, or we decide it’s not important, not a substantial part of the whole feature, and therefore doesn’t need to be documented/tracked in that side project and use Bug-Url-less commit to master.</div><div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><div class="">and maybe consider adding tools/verification for the new tools.</div></div></div></div></div></blockquote></div><div><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><div class=""><br class=""></div><div class="">But it doesn't make sense to start supporting more than one issue tracker, we have too many systems already, so if we move, then all projects </div><div class="">needs to move. </div></div></div></div></div></blockquote><div><br class=""></div>github issue is fairly common so if we want to support something else in addition to bugzilla Bug-Url this would be a good candidate</div><div><br class=""></div><div>Thanks,</div><div>michal</div><div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><div class=""> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><span class=""><div class=""><br class=""></div><div class=""> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><div class=""> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><div dir="ltr" class=""><div class="">Thanks,</div><span class="m_-7207547829882275409m_-2730009894664891844HOEnZb"><font color="#888888" class=""><div class=""><br class=""></div><div class="">-- <br class=""><div class="m_-7207547829882275409m_-2730009894664891844m_-7702639009489894392gmail_signature"><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class="">Sandro Bonazzola<br class="">Better technology. Faster innovation. Powered by community collaboration.<br class="">See how it works at <a href="http://redhat.com/" target="_blank" class="">redhat.com</a></div></div></div></div></div></div></div></div>
</div></font></span></div>
<br class=""></span>______________________________<wbr class="">_________________<br class="">
Devel mailing list<br class="">
<a href="mailto:Devel@ovirt.org" target="_blank" class="">Devel@ovirt.org</a><br class="">
<a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank" class="">http://lists.ovirt.org/mailman<wbr class="">/listinfo/devel</a><span class="m_-7207547829882275409HOEnZb"><font color="#888888" class=""><br class=""></font></span></blockquote></div><span class="m_-7207547829882275409HOEnZb"><font color="#888888" class=""><br class=""><br clear="all" class=""><div class=""><br class=""></div>-- <br class=""><div class="m_-7207547829882275409m_-2730009894664891844gmail_signature" data-smartmail="gmail_signature"><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class="">Eyal Edri<br class="">Associate Manager</div><div class="">RHV DevOps<br class="">EMEA ENG Virtualization R&D<br class="">Red Hat Israel<br class=""><br class="">phone: <a href="tel:+972%209-769-2018" value="+97297692018" target="_blank" class="">+972-9-7692018</a><br class="">irc: eedri (on #tlv #rhev-dev #rhev-integ)</div></div></div></div></div></div></div>
</font></span></div></div>
</blockquote></span></div><span class=""><br class=""><br clear="all" class=""><div class=""><br class=""></div>-- <br class=""><div class="m_-7207547829882275409gmail_signature" data-smartmail="gmail_signature"><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class="">Sandro Bonazzola<br class="">Better technology. Faster innovation. Powered by community collaboration.<br class="">See how it works at <a href="http://redhat.com/" target="_blank" class="">redhat.com</a></div></div></div></div></div></div></div></div>
</span></div></div>
</blockquote></div><br class=""><br clear="all" class=""><div class=""><br class=""></div>-- <br class=""><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class="">Eyal Edri<br class="">Associate Manager</div><div class="">RHV DevOps<br class="">EMEA ENG Virtualization R&D<br class="">Red Hat Israel<br class=""><br class="">phone: +972-9-7692018<br class="">irc: eedri (on #tlv #rhev-dev #rhev-integ)</div></div></div></div></div></div></div>
</div></div>
_______________________________________________<br class="">Devel mailing list<br class=""><a href="mailto:Devel@ovirt.org" class="">Devel@ovirt.org</a><br class="">http://lists.ovirt.org/mailman/listinfo/devel</div></blockquote></div><br class=""></body></html>