From: Michael Palimaka <kensington@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: stable-bot is down. Temporary? Forever? Can we have a contacts page for it?
Date: Mon, 7 Oct 2019 22:29:39 +1100 [thread overview]
Message-ID: <44e7f975-7844-45c6-4d33-15c688b7a5e0@gentoo.org> (raw)
In-Reply-To: <robbat2-20191003T192350-127606167Z@orbis-terrarum.net>
On 10/4/19 5:32 AM, Robin H. Johnson wrote:
> On Wed, Oct 02, 2019 at 08:43:44AM -0700, Matt Turner wrote:
>> On Thu, Sep 26, 2019 at 12:29 AM Sergei Trofimovich <slyfox@gentoo.org> wrote:
>>>
>>> I noticed that stable-bot stopped marking bugs as verified for stbilization.
>>> Example:
> ...
>> It looks like it is working now, but I think we really should know a few things:
>>
>> (1) Who maintains it
>> (2) Where the code is
>> (3) and perhaps what happened to bring it down
>>
>> It's a pretty important piece of infrastructure that we've come to
>> rely on, so it should be treated as such.
> Can I take this opportunity to ask people to help populate the Service
> Catalog?
> https://wiki.gentoo.org/wiki/Project:Infrastructure/Service_Catalog
>
Is it appropriate to list services that are not managed by infra on this
page?
next prev parent reply other threads:[~2019-10-07 11:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 7:28 [gentoo-dev] stable-bot is down. Temporary? Forever? Can we have a contacts page for it? Sergei Trofimovich
2019-10-02 15:43 ` Matt Turner
2019-10-03 19:32 ` Robin H. Johnson
2019-10-04 3:09 ` bman
2019-10-04 11:30 ` Mike Gilbert
2019-10-07 11:29 ` Michael Palimaka [this message]
2019-10-07 19:11 ` [gentoo-dev] " Robin H. Johnson
2019-10-07 20:21 ` Andreas K. Huettel
2019-10-08 11:57 ` Michael Palimaka
2019-10-08 12:22 ` Rich Freeman
2019-10-08 15:46 ` Alec Warner
2019-10-07 11:27 ` Michael Palimaka
2019-12-24 12:19 ` Sergei Trofimovich
2019-12-06 16:15 ` [gentoo-dev] " Matt Turner
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=44e7f975-7844-45c6-4d33-15c688b7a5e0@gentoo.org \
--to=kensington@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