Re: Add a rule to have a compose when Fedora branched

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

 



On 19. 09. 19 23:29, Kevin Fenzi wrote:
* Stop rawhide composes until we have a branched compose. This may
not
be needed with the change to make rawhide use 'rawhide' and not the
number, but we should consider it if we don't have a compose to avoid
confusion.
Where should I signed this?:)

But now for real, from my understanding you are basically proposing
improved version of what Miro mentioned somewhere here in the thread.
That means make freeze after branching. I definitely agree on that.
Well, I was not saying we should go into Beta freeze immediately and
stay in it until Beta is out. I was just saying we should have a
temporary freeze right after branching until we have a completed
branched compose. Then we can open things up again until Beta freeze.

To clarify: That's exactly what I meant.

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
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