Re: [Test-Announce] Fedora 29 Final is GO

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

 



On Fri, Oct 26, 2018 at 6:22 AM, Peter Robinson <pbrobinson@xxxxxxxxx> wrote:
>> On 25/10/2018 20:58, Ben Cotton wrote:
>> > The Fedora 29 Final RC1.2 compose [1] is GO and will to be shipped
>> > live on Tuesday, October 30, 2018.
>> >
>> > For more information please check the Go/No-Go meeting minutes [2] or logs [3].
>> >
>> > Thank you to everyone who has worked on this release.
>> >
>> > [1] http://dl.fedoraproject.org/pub/alt/stage/29_RC-1.2/
>> > [2] https://meetbot.fedoraproject.org/fedora-meeting-1/2018-10-25/f29-final-go_no_go-meeting.2018-10-25-17.03.html
>> > [3] https://meetbot.fedoraproject.org/fedora-meeting-1/2018-10-25/f29-final-go_no_go-meeting.2018-10-25-17.03.log.html
>> >
>>
>> Is there any reason why
>> https://koji.fedoraproject.org/koji/taskinfo?taskID=30445005 has been
>> canceled? I don't see any obvious reason in the logs and I really want
>> the Astronomy Spin to be shipped… Normally that spin builds fine, see
>> latest daily build:
>> https://koji.fedoraproject.org/koji/taskinfo?taskID=30453015
>>
>> In addition I want to note that we have many broken spins like the
>> Python Classroom and Design. I'm not sure whether it is a good idea to
>> ignore this, also for marketing reasons :(
>
> Yes, I agree, I am at a loss as to why it was signed off as well,
> there was blockers like "Be able to apply updates using the desktop
> mechanism" that were seemingly ignored with broken gnome-software,
> plus numerous other issues. I don't feel it was ready but clearly
> someone had some agenda to ram it on through despite the issues.

I read the minutes and my take away is almost 180 degrees from your
conclusion. The process was rational and logical, and reached a
reasonable conclusion objectively. There were valid subjective reasons
to postpone.

There was a gnome-software bug proposed as a blocker. It was
determined not to be a blocker. So it's not correct to say it was a
blocker and that it was ignored. And that there were numerous other
issues (?) that were also not blockers, isn't something I can parse.

On what process basis, including release criteria, whether existing
now or one you'd like to propose, should this release have been held
up?

Chris Murphy
_______________________________________________
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