From: "\"Paweł Hajdan, Jr.\"" <phajdan.jr@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Gentoo Bugday
Date: Tue, 26 Feb 2013 18:01:06 -0800 [thread overview]
Message-ID: <512D68E2.1030501@gentoo.org> (raw)
In-Reply-To: <CAOgmxWyOg4cERMDoGOWaU=AWkXqf=AEuhF-J+HfAM9sHss52dA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 784 bytes --]
On 2/26/13 4:39 PM, Pavlos Ratis wrote:
> I would like to announce you a new try to 'revive' the Bugday event.
This is excellent! Thank you for your work on this.
> I have listed some maintainer-wanted and maintainer-need bugs and
> Bugzilla admins also re-enabled the bugday flag. I would like to ask
> the Gentoo project teams to start using this flag to their bugs that
> think that are good to start and enable the flag at them. It would be
> great to a have a really big list with 'good to start' bugs.
I'm going to look over chromium@ bugs, but consider also arch testing
bugs (STABLEREQ) relevant - just avoid people making too much noise.
1-2 success reports are enough, and the more testing we can get before
actually stabilizing, the better.
Paweł
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 203 bytes --]
next prev parent reply other threads:[~2013-02-27 2:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 0:39 [gentoo-dev] Gentoo Bugday Pavlos Ratis
2013-02-27 2:01 ` "Paweł Hajdan, Jr." [this message]
2013-02-27 3:14 ` [gentoo-dev] " Michael Palimaka
2013-02-27 6:28 ` Alec Warner
2013-02-27 10:19 ` Theo Chatzimichos
2013-02-27 18:57 ` Pavlos Ratis
2013-02-27 19:00 ` Peter Stuge
2013-02-27 19:40 ` Tom Wijsman
2013-02-27 21:30 ` Peter Stuge
2013-02-27 23:04 ` Tom Wijsman
2013-02-28 0:20 ` Peter Stuge
2013-02-28 1:07 ` Tom Wijsman
2013-02-28 2:14 ` Pavlos Ratis
2013-02-28 16:31 ` Roy Bamford
2013-02-28 11:33 ` Sergey Popov
2013-02-28 15:47 ` Pavlos Ratis
2013-02-27 9:07 ` [gentoo-dev] " Alexander Berntsen
2013-02-27 15:07 ` Peter Stuge
2013-02-27 19:12 ` Roy Bamford
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=512D68E2.1030501@gentoo.org \
--to=phajdan.jr@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox