<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Feb 24, 2015 at 11:24 AM, Dennis Gilmore <span dir="ltr"><<a href="mailto:dennis@ausil.us" target="_blank">dennis@ausil.us</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Today is also the Alpha freeze[4]. This means that only packages which<br>
fix accepted blocker or freeze exception bugs[5][6] will be marked as<br>
'stable' and included in the Alpha composes. Other builds will remain<br>
in updates-testing until the Alpha release is approved, at which point<br>
the Alpha freeze is lifted and packages can move to 'stable' as usual<br>
until the Beta freeze.<br></blockquote></div><br></div><div class="gmail_extra">I have a question on how I'm supposed to handle a new package. I was working on packaging iwyu [1] and it built for all of the target releases except for F22 because of some gcc 5.0 issues. It appears that the last one has been resolved [2], so how do I handle this situation? Do I just wait until the alpha freeze is over to build iwyu for F22? Or should I use a buildroot override?<br></div><div class="gmail_extra">Thanks,<br></div><div class="gmail_extra">Dave<br><br>[1] <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1091659">https://bugzilla.redhat.com/show_bug.cgi?id=1091659</a><br>[2] <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1190329#c2">https://bugzilla.redhat.com/show_bug.cgi?id=1190329#c2</a></div></div>