9:38 a.m.
According to the Fedora 30 schedule[1], the 100% code complete
deadline[2] for Changes is Tuesday, 5 March. The beta freeze[3]
takes effect on this date as well. All Changes should be in "ON_QA"
state by then.
[1] https://fedoraproject.org/wiki/Releases/30/Schedule
[2]
https://fedoraproject.org/wiki/Changes/Policy#Change_Checkpoint:_100.25_c...
[3] https://fedoraproject.org/wiki/Milestone_freezes
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
1:11 p.m.
On Tue, 2019-02-26 at 10:38 -0500, Ben Cotton wrote:
According to the Fedora 30 schedule[1], the 100% code complete
deadline[2] for Changes is Tuesday, 5 March. The beta freeze[3]
takes effect on this date as well. All Changes should be in "ON_QA"
state by then.
I still haven't any compose for F30 completed, we should have time to
build some packages against f30 buildroots , this situation also
happened in F29 .
Question why composer are broken , when is most needed ?
What I mean is Beta freeze should be postponed after two weeks of
composer start to work . Given 2 week to packages maintainers fix the
FTBFS packages etc .
[1] https://fedoraproject.org/wiki/Releases/30/Schedule
[2]
https://fedoraproject.org/wiki/Changes/Policy#Change_Checkpoint:_100.25_c...
[3] https://fedoraproject.org/wiki/Milestone_freezes
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
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@lists.fedoraproject.org
--
Sérgio M. B.
6:09 p.m.
On 2/26/19 11:11 AM, Sérgio Basto wrote:
On Tue, 2019-02-26 at 10:38 -0500, Ben Cotton wrote:
> According to the Fedora 30 schedule[1], the 100% code complete
> deadline[2] for Changes is Tuesday, 5 March. The beta freeze[3]
> takes effect on this date as well. All Changes should be in "ON_QA"
> state by then.
I still haven't any compose for F30 completed, we should have time to
We have. The compose on the 24th finished and synced out.
build some packages against f30 buildroots , this situation also
happened in F29 .
The buildroot is in koji and is always updated, or do you mean something
else?
Question why composer are broken , when is most needed ?
Because we don't have gating and everyone drops tons of changes in.
What I mean is Beta freeze should be postponed after two weeks of
composer start to work . Given 2 week to packages maintainers fix the
FTBFS packages etc .
You can work on FTBFS anytime... thats not constrained by the compose.
kevin
6:58 p.m.
On Tue, 2019-02-26 at 16:09 -0800, Kevin Fenzi wrote:
On 2/26/19 11:11 AM, Sérgio Basto wrote:
> On Tue, 2019-02-26 at 10:38 -0500, Ben Cotton wrote:
> > According to the Fedora 30 schedule[1], the 100% code complete
> > deadline[2] for Changes is Tuesday, 5 March. The beta freeze[3]
> > takes effect on this date as well. All Changes should be in
> > "ON_QA"
> > state by then.
>
> I still haven't any compose for F30 completed, we should have time
> to
We have. The compose on the 24th finished and synced out.
> build some packages against f30 buildroots , this situation also
> happened in F29 .
The buildroot is in koji and is always updated, or do you mean
something
else?
yes, without composes, buildroots on copr, mock and RPMFusion aren't
updated .
> Question why composer are broken , when is most needed ?
Because we don't have gating and everyone drops tons of changes in.
> What I mean is Beta freeze should be postponed after two weeks of
> composer start to work . Given 2 week to packages maintainers fix
> the
> FTBFS packages etc .
You can work on FTBFS anytime... thats not constrained by the
compose.
Without buildroots updated is much more difficult test the builds.
Sorry for my bad mood , I'm tired, but since I'm on reflection , I
think after mass rebuild with new gcc we should wait a little more
until mass branching, new gcc always have a lot of FTBFS
No branched composes also means no testing installations, dnf broken
deps and debug a lot of things .
Many thanks,
--
Sérgio M. B.
2:44 p.m.
On 2/26/19 4:58 PM, Sérgio Basto wrote:
On Tue, 2019-02-26 at 16:09 -0800, Kevin Fenzi wrote:
> On 2/26/19 11:11 AM, Sérgio Basto wrote:
>> On Tue, 2019-02-26 at 10:38 -0500, Ben Cotton wrote:
>>> According to the Fedora 30 schedule[1], the 100% code complete
>>> deadline[2] for Changes is Tuesday, 5 March. The beta freeze[3]
>>> takes effect on this date as well. All Changes should be in
>>> "ON_QA"
>>> state by then.
>>
>> I still haven't any compose for F30 completed, we should have time
>> to
>
> We have. The compose on the 24th finished and synced out.
>
>> build some packages against f30 buildroots , this situation also
>> happened in F29 .
>
> The buildroot is in koji and is always updated, or do you mean
> something
> else?
yes, without composes, buildroots on copr, mock and RPMFusion aren't
updated .
Yeah, sadly true. You could use the fedora koji buildroot repo, but I
don't think we want to have too many people hit it.
Without buildroots updated is much more difficult test the builds.
Sorry for my bad mood , I'm tired, but since I'm on reflection , I
think after mass rebuild with new gcc we should wait a little more
until mass branching, new gcc always have a lot of FTBFS
Well, I don't think any of the compose failures were actually due to
gcc. It's mostly I think everyone dropping in there work so it lands in
f30, and it's up to us to integrate it and get composes working.
No branched composes also means no testing installations, dnf broken
deps and debug a lot of things .
I don't disagree, but we are trying as best we can to get composes
working. I don't think a delay would have helped in particular. People
finishing and landing things earlier so we had less of a chain of issues
would have helped, but I have no idea how to get that to happen. ;(
kevin
12:56 p.m.
Can someone wake me once beta is released, the time between branching and beta isn't
enough to do anything!
1873
days inactive
1878
days old
5 comments
4 participants
participants (4)
-
Ben Cotton -
Kevin Fenzi -
Leigh Scott -
Sérgio Basto