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 5:14 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

That would be good, however I don't know how it is related to
lifecycle of distro.

P.S. would be great if someone finishes packaging of it (I did a lot
of work here, but not everything).

> * fix the compose speed (target: one hour!)

Do we have analysis of what is taking how much time?

> * really actually for real gated Rawhide

Is the "creating side tag for chain builds or by automated requests"
is planned here?
When I deal with rust packages, I often need to build some update
which will break other packages and I need to fix them, but if
something will prevent going that build in buildroot.

> * better CI pipeline tests for everything

Does it mean that finally someone will make it usable? Do we have
definition of "better"? I've tried to use CI for all rust-* packages,
but it is basically unusable.

* No way to re-trigger tests
* Koji repo is broken even is enabled
(https://pagure.io/fedora-ci/general/issue/14, no single comment for >
0.5 month)
* Doesn't re-trigger after dependency changes
* No way to tell that set of tests should be run on some file pattern
(copy-cating same tests folder to 480 packages is not much fun)

> * define a base platform -- Red Hat wants to focus resources here

Can you elaborate?

> * better tooling for non-base deliverables

Are Ursa Major and Freshmaker included in here?

> * better metrics for everything
>
>
> Please read https://fedoraproject.org/wiki/Objectives/Lifecycle/Problem_statements
> and comment in this thread.

I would appreciate having this thread on discourse because since
introduction it is my main place where I try to have such
conversations.

>
> --
> 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