From: Trevor Woerner <trevor.woerner@linaro.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: bug scrub - RFC
Date: Thu, 09 Jan 2014 10:38:22 -0500 [thread overview]
Message-ID: <52CEC26E.1080603@linaro.org> (raw)
In-Reply-To: <CAP9ODKpxHnLq1PLJJp2LsGt4WGD9Q159Jo_nQnNNaLy1gzDXSw@mail.gmail.com>
On 01/09/14 10:34, Otavio Salvador wrote:
>
> On Thu, Jan 9, 2014 at 1:07 PM, Trevor Woerner
> <trevor.woerner@linaro.org <mailto:trevor.woerner@linaro.org>> wrote:
>
> On 01/09/14 05:56, Jack Mitchell wrote:
> > On 08/01/14 23:20, Trevor Woerner wrote:
> >> questions:
> >> 1) Currently it has been suggested this should be a 2-day
> event, should
> >> these two days be during the week or over a weekend? In either
> case,
> >> which 2 days?
> >>
> > If it's two days long then why don't you do the best of both
> worlds and
> > have a Friday/Saturday or Sunday/Monday combination?
>
> I was thinking of doing it either fully during the week, or fully on a
> weekend since my feeling is that most people either work with OE/Yocto
> during the weekdays or on the weekend. There's nothing to say we
> couldn't run this "bug scrub" during the week, then run a second "bug
> scrub" 2 months from now on a weekend (or visa versa).
>
>
> Maybe mix it, Friday, Saturday, Sunday, Monday.
>
> So we give in a single 'event' opportunity to both.
>
Okay, I can agree to that.
How about targeting next weekend (Jan 17-18 2014). Would that be too soon?
next prev parent reply other threads:[~2014-01-09 15:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 23:20 bug scrub - RFC Trevor Woerner
2014-01-09 10:56 ` Jack Mitchell
2014-01-09 15:07 ` Trevor Woerner
2014-01-09 15:34 ` Otavio Salvador
2014-01-09 15:38 ` Trevor Woerner [this message]
2014-01-10 2:47 ` Philip Balister
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52CEC26E.1080603@linaro.org \
--to=trevor.woerner@linaro.org \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.