From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: x86@gentoo.org, ppc@gentoo.org, ia64@gentoo.org,
alpha@gentoo.org, sparc@gentoo.org
Subject: Re: [gentoo-dev] Hey arch teams, we need your input!
Date: Sat, 11 Apr 2015 22:51:51 +0200 [thread overview]
Message-ID: <1428785511.2041.123.camel@gentoo.org> (raw)
In-Reply-To: <201504112150.13880.dilfridge@gentoo.org>
El sáb, 11-04-2015 a las 21:50 +0200, Andreas K. Huettel escribió:
> Hi all,
>
> the debate about arches, keywording and stabilization procedures is
> coming up again.
>
> People have told me that the whole debate seems to turn into some sort
> of arch-team bashing. That is definitely not the plan. Also,
> supporting many different types of hardware is actually one of the
> strong points of Gentoo.
>
> So, it would be absolutely great to have more feedback from the arch
> teams, especially suggestions
> * how to improve procedures,
> * where you see the main problems, and
> * where you don't see problems...
>
> Please make your voice heard. Noone wants to overrule an active team.
>
> Cheers,
> Andreas
>
> PS. I've ommitted amd64, hppa, and arm from the manual CC list because
> these are the stable arches I'm definitely not worried about.
> Obviously feedback is appreciated anyway.
>
I think we need a common place to share all the scripts we are needing
to use to:
- Stabilize a bunch of packages from different bug reports
- Stabilize big lists from *one* bug report
- All the bug handling (unCC arches when needed, close the bug when it's
the last arch)
- The scripts running "repoman full" on the stable candidates to report
if they are not ok due to missing deps.
- ...
And, ideally, that multiple script should be unified if possible once we
can see them all in that repo and take the best from them :)
next prev parent reply other threads:[~2015-04-11 20:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-11 19:50 [gentoo-dev] Hey arch teams, we need your input! Andreas K. Huettel
2015-04-11 20:51 ` Pacho Ramos [this message]
2015-04-11 21:08 ` Mikle Kolyada
2015-04-26 9:59 ` Pacho Ramos
2015-04-26 12:04 ` Rich Freeman
2015-04-26 12:12 ` Pacho Ramos
2015-04-26 16:20 ` Jeroen Roovers
2015-04-28 9:07 ` Tobias Klausmann
2015-05-15 8:51 ` Pacho Ramos
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=1428785511.2041.123.camel@gentoo.org \
--to=pacho@gentoo.org \
--cc=alpha@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=ia64@gentoo.org \
--cc=ppc@gentoo.org \
--cc=sparc@gentoo.org \
--cc=x86@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