Can someone wake me once beta is released, the time between branching and beta
isn't enough to do anything!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct
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 Tu
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]
> > >
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"
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
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/w
According to the Fedora 29 schedule[1], the 100% code complete
deadline[2] for Changes is Tuesday, 28 August. 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/29/Schedule
[2]
https://fedoraproject.org
