On Thu, Oct 12, 2017 at 10:28:01AM +0530, Nithya Balachandran wrote:
> On 12 October 2017 at 10:12, Raghavendra Talur wrote:
>
> > On Wed, Oct 11, 2017 at 8:35 PM, Shyam Ranganathan
> > wrote:
> > > Hi,
> > >
> > > Recently I was in some conversations that mentioned having to hunt for
> > the
>
On Thu, Oct 12, 2017 at 6:09 PM, Shyam Ranganathan wrote:
> On 10/12/2017 12:58 AM, Nithya Balachandran wrote:
>>
>> > - When to mark the blocker bug as dependent on another bug:
>> >
>> > Blockers are meant to track *just* blockers for a major or minor
>> release,
>> > not
On 10/12/2017 12:58 AM, Nithya Balachandran wrote:
> - When to mark the blocker bug as dependent on another bug:
>
> Blockers are meant to track *just* blockers for a major or minor
release,
> not all bugs that are a part of the release. Hence when a bug is
actually a
On 12 October 2017 at 10:12, Raghavendra Talur wrote:
> On Wed, Oct 11, 2017 at 8:35 PM, Shyam Ranganathan
> wrote:
> > Hi,
> >
> > Recently I was in some conversations that mentioned having to hunt for
> the
> > mail that announced the blocker bug for a release, when there is a need
> to
> > ma
On Wed, Oct 11, 2017 at 8:35 PM, Shyam Ranganathan wrote:
> Hi,
>
> Recently I was in some conversations that mentioned having to hunt for the
> mail that announced the blocker bug for a release, when there is a need to
> mark a bug as a blocker for that release.
>
> This need not be done as here
Hi,
Recently I was in some conversations that mentioned having to hunt for
the mail that announced the blocker bug for a release, when there is a
need to mark a bug as a blocker for that release.
This need not be done as here is the shortcut (if you did not know) on
how to find the blocker,