Re: Proposal: delay F31 release to work out infrastructure and lifecycle challenges

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Nov 26, 2018 at 4:05 PM Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> wrote:
>
> On Fri, Nov 16, 2018 at 09:50:33AM -0500, Paul Frields wrote:
> > Here's the summary from the page, which proposes we pause the release
> > after F30 for these efforts:
>
> I know it was a big time-off holiday week in the US, but I expected a little
> more interest in this post. Perhaps it seemed like too much text to digest
> along with turkey and stuffing. :) I'm highlighting it with a subject
> reflecting the big, direct impact, and here's some other top-level
> proposals:
>
> * embrace Taiga (an open source kanban tool) for project planning
> * fix the compose speed (target: one hour!)

Can I have a unicorn? Everyone wants this bug absolutely no one has
done analysis. The fact of the matter is that the compose has a LOT of
I/O and I/O is slow and the cost to upgrade the infrastructure to get
high through put I/O is expensive and no one has ever offered the
budget to resolve that problem. The fact of the matter with this is
that we now produce a lot of release artifacts and that takes time,
some of it can probably be run more in parallel, and possibly some
things run at different times but without a combination of investment
in infrastructure, and maybe even hacking and slashing of components
this is not simply a check box.

For example the IoT compose takes around an hour but ATM we currently
produce 5 artifacts, mostly in parallel, and don't do things like
newRepo for the base rpms because we consume that from the main
compose.

> * really actually for real gated Rawhide
> * better CI pipeline tests for everything
> * define a base platform -- Red Hat wants to focus resources here
> * better tooling for non-base deliverables
> * better metrics for everything

They are very nice top level ideas, but each of those components need
to have in depth analysis and not just the hand wavy overview in the
link below.

> Please read https://fedoraproject.org/wiki/Objectives/Lifecycle/Problem_statements
> and comment in this thread.
>
> --
> Matthew Miller
> <mattdm@xxxxxxxxxxxxxxxxx>
> Fedora Project Leader
> _______________________________________________
> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux