On 16 June 2011 23:38, Michael Hope <michael.h...@linaro.org> wrote: > On Thu, Jun 16, 2011 at 11:06 PM, Fathi Boudra <fathi.bou...@linaro.org> > wrote: >> On 14 June 2011 21:53, Michael Hope <michael.h...@linaro.org> wrote: >>> How does this relate to working group outputs? >>> >>> Here's my process BTW: >>> https://wiki.linaro.org/WorkingGroups/ToolChain/BugProcess >>> >>> It's unusual for a bug to be a release blocker as there's normally >>> some type of work around. I'd normally only stop or respin a release >>> if the bug is embarrassing (which I guess is equivalent to Critical :) >> >> A bug can be qualified as a release blocker after the WG release, >> probably during Platform integration coming after your component >> release. It will result that the bug will be under the release team >> radar and we'll work together to fix it in time for the Platform >> release, most likely a respin is needed. > > I'd prefer to add a work-around to the package than respin. If no > work around exists and the package is important enough then we can fix > and respin, but note that any change to the compiler may affect a > different package.
I guess it will be discussed on a case by case basis between you and Ricardo. Otherwise, sounds good to me. Cheers, Fathi _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
