But is it correct chromium practice to actually close the blockee
while it is being blocked?
To cut to the chase, I'm against having a "master" bug that represents
a UI change on all platforms. I've found it works better for me to
have one bug for each platform that are all independent.
I guess I just hate having bugs linger for a long time with tons of
changes against them.
- a
On Tue, Oct 20, 2009 at 11:49 AM, Anthony LaForge <lafo...@google.com> wrote:
> Nico beat me to it, but that's precisely correct, you just need to add the
> child bug ids to the blocked by line in the parent bug.
> Kind Regards,
>
> Anthony Laforge
> Technical Program Manager
> Mountain View, CA
>
>
> On Tue, Oct 20, 2009 at 11:30 AM, Nico Weber <tha...@chromium.org> wrote:
>>
>> In the blockee, enter the blockers in the "Blocked by" line at the bottom.
>>
>> On Tue, Oct 20, 2009 at 11:21 AM, Aaron Boodman <a...@chromium.org> wrote:
>> >
>> > On Tue, Oct 20, 2009 at 11:16 AM, Ben Goodger (Google)
>> > <b...@chromium.org> wrote:
>> >> - mark the new bug as blocking the original bug for the work, even if
>> >> the
>> >> original bug is now or soon will be closed.
>> >
>> > Can you explain more what you mean by this? What is the way to mark a
>> > bug as blocking? How can the blockee be closed if it is blocked by
>> > another bug that is open?
>> >
>> > - a
>> >
>> > >
>> >
>>
>> >>
>
>
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
