From: "Frank Ch. Eigler" <fche@elastic.org>
To: Carlos O'Donell <carlos@redhat.com>
Cc: overseers@sourceware.org, Florian Weimer <fweimer@redhat.com>
Subject: Re: Choice of distribution for new sourceware.org server?
Date: Thu, 06 Feb 2020 14:49:00 -0000 [thread overview]
Message-ID: <20200206144908.GG97355@elastic.org> (raw)
In-Reply-To: <c2332d37-c4c7-3475-d5e7-19824f852772@redhat.com>
Hi -
> >> How much non-distro software is there on sourceware?
> > Well, quite a bit.
>
> If non-distro softare impacts our maintenance costs, should we be evaluating
> the list of non-distro software for value vs. cost?
We evaluate regularly. It's not just software that substitutes for
distro bits (there's only a bit of that). Remember things like
multiple wikis, bugzilla.
> >> When you say "activity" do you mean that users would be impacted
> >> once every 8 months for a small window of downtime?
> >
> > Probably, if nothing goes wrong. And if there's an incompatible
> > rebase of python or php or whatever, then we (?) have to fix the
> > thing. There is a downside to upgrade churn, in terms of our
> > manpower.
>
> Best practice is to have a production and development server to
> avoid these kinds of problems and shake out such changes.
> Do we have 2 servers now?
rawhide level upgrade churn has to bring tangible value that is in
excess of the costs (to all the parties, not just users).
> In which case RHEL8 with ELS as an option is even more valuable?
> In summary:
> - Why not stick with RHEL8 to get ELS and avoid CentOS 8 early phase out.
Already said I'll look into moving from centos8 to rhel8. centos
lifespan does not look materially different from rhel.
- FChE
next prev parent reply other threads:[~2020-02-06 14:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 1:05 Carlos O'Donell
2020-02-06 1:30 ` Christopher Faylor
2020-02-06 1:34 ` Frank Ch. Eigler
2020-02-06 1:51 ` Carlos O'Donell
2020-02-06 2:02 ` Frank Ch. Eigler
2020-02-06 2:16 ` Carlos O'Donell
2020-02-06 14:49 ` Frank Ch. Eigler [this message]
2020-02-06 15:10 ` Carlos O'Donell
2020-02-06 15:19 ` Frank Ch. Eigler
2020-02-06 16:36 ` Carlos O'Donell
2020-02-06 16:46 ` Christopher Faylor
2020-02-06 16:49 ` Frank Ch. Eigler
2020-02-06 1:45 ` Carlos O'Donell
2020-02-06 6:05 ` Christopher Faylor
2020-02-06 14:50 ` Carlos O'Donell
2020-02-06 15:11 ` Lukas Berk
2020-02-06 15:22 ` Carlos O'Donell
2020-02-06 15:20 ` Christopher Faylor
2020-02-06 17:05 ` Carlos O'Donell
2020-02-06 18:28 ` Joseph Myers
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=20200206144908.GG97355@elastic.org \
--to=fche@elastic.org \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=overseers@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).