<p dir="ltr">Can we have a possibility to select field like "affected version" and have it such that multiple versions can be specified</p>
<div class="gmail_quote">On Apr 18, 2016 3:27 AM, "Burton, Ross" <<a href="mailto:ross.burton@intel.com">ross.burton@intel.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>At the moment we don't really have a policy for oe-core bugs in <a href="http://bugzilla.yoctoproject.org" target="_blank">bugzilla.yoctoproject.org</a> that apply to multiple releases, for example <a href="https://bugzilla.yoctoproject.org/show_bug.cgi?id=9400" target="_blank">https://bugzilla.yoctoproject.org/show_bug.cgi?id=9400</a>. This is a CVE bug that should be fixed in all supported branches, and indeed Sona has sent patches for Fido/Dizzy/Jethro/master. Of course now we've got to track where these patches are in the submission process and ensure that we don't drop any of these, but bugzilla only has a single target milestone for each bug.</div><div><br></div><div>I propose that for bugs such as this we file a bug report for master and then clone it (there's a Clone This Bug button at the bottom) for each stable release that is affected. Then each bug can have it's own target milestone set and we can be sure that the patches don't get left out of being merged and that QA can effectively verify each branch.</div><div><br></div><div>Any objection or feedback? (the first person to suggest moving to Jira gets to manually review all CVEs from CVE-1999-0001 onwards are fixed in krogoth).</div><div><br></div><div>Ross</div></div>
<br>--<br>
_______________________________________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org">Openembedded-core@lists.openembedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" rel="noreferrer" target="_blank">http://lists.openembedded.org/mailman/listinfo/openembedded-core</a><br>
<br></blockquote></div>