From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-dev] arches.desc & GLEP 72 (was: Re: [gentoo-project] Items for Council Agenda, May 14)
Date: Mon, 08 May 2017 13:46:00 +0200 [thread overview]
Message-ID: <3588979.Z3kVisoUaO@porto> (raw)
In-Reply-To: <1494189051.1963.6.camel@gentoo.org>
Am Sonntag, 7. Mai 2017, 22:30:51 CEST schrieb Michał Górny:
>
> Oh, one more thing that I've forgot to mention in the original mail.
> It'd probably be useful to solve two disjoint problems:
>
> a. whether CI should enforce correct depgraph and how,
>
Well, my approach for this would be that CI should enforce the same things as
Repoman.
Which means
* stable: CI enforces separate deptrees for arch and ~arch
* (testing, now) mixed: CI enforces deptree for ~arch (treating arch as ~arch)
* unstable: CI enforces deptree for ~arch, CI errors on encountering arch
>
> 2. stable depgraph is broken and we don't care (i.e. we don't CC
> the arch and drop old stable versions if necessary).
Keep the arch on "mixed", or drop all stable keywords in one commit and then
set it to "unstable".
>
> b. whether we should request stabilizing packages.
>
>
> 1. stable depgraph is broken but we want to fix it (i.e. should CC
> the arch on stablereqs),
Well... so far my approach would have been,
* keep arch (testing) mixed, until the arch team says "good to go",
* then make hard switch to stable, and start with stablerequests
We could, however, add one more column *only* for the (testing) mixed case,
which states whether stabilization requests are required.
(Only for the mixed case, since for "stable" this is always yes, and for
"unstable" it makes no sense.)
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer (council, perl, libreoffice)
next prev parent reply other threads:[~2017-05-08 11:45 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-29 17:00 [gentoo-project] Items for Council Agenda, May 14 Anthony G. Basile
2017-04-30 13:52 ` Andreas K. Huettel
2017-05-03 21:26 ` Daniel Campbell
2017-05-06 14:34 ` arches.desc & GLEP 72 (was: Re: [gentoo-project] Items for Council Agenda, May 14) Andreas K. Huettel
2017-05-06 16:35 ` [gentoo-dev] " Michał Górny
2017-05-06 17:36 ` Andreas K. Huettel
2017-05-06 20:23 ` Michał Górny
2017-05-07 2:53 ` Kent Fredric
2017-05-07 20:30 ` Michał Górny
2017-05-08 11:46 ` Andreas K. Huettel [this message]
2017-05-13 0:03 ` Andreas K. Huettel
2017-05-13 7:44 ` Michał Górny
2017-05-13 22:48 ` Andreas K. Huettel
2017-05-07 15:47 ` Roy Bamford
2017-05-14 15:38 ` Andreas K. Huettel
2017-05-11 7:17 ` [gentoo-project] Items for Council Agenda, May 14 Matthias Maier
2017-05-11 7:52 ` NP-Hardass
2017-05-11 8:02 ` Michał Górny
2017-05-11 9:16 ` Raymond Jennings
2017-05-11 10:08 ` Kent Fredric
2017-05-11 10:52 ` Rich Freeman
2017-05-11 15:03 ` Gregory Woodbury
2017-05-11 16:45 ` Luis Ressel
2017-05-11 19:57 ` Rich Freeman
2017-05-11 20:24 ` William L. Thomson Jr.
2017-05-11 20:28 ` Michał Górny
2017-05-13 9:26 ` Kent Fredric
2017-05-14 1:46 ` M. J. Everitt
2017-05-11 18:55 ` Roy Bamford
2017-05-11 19:09 ` Raymond Jennings
2017-05-11 19:54 ` Rich Freeman
2017-05-13 9:14 ` Kent Fredric
2017-05-11 20:25 ` William L. Thomson Jr.
2017-05-11 23:07 ` Daniel Campbell
2017-05-12 8:52 ` Roy Bamford
2017-05-12 10:41 ` Andreas K. Huettel
2017-05-13 9:36 ` Daniel Campbell
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=3588979.Z3kVisoUaO@porto \
--to=dilfridge@gentoo.org \
--cc=gentoo-project@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