----- Original Message -----
> From: "Miro Hrončok" <mhron...@redhat.com>
> To: devel@lists.fedoraproject.org
> Cc: "Mohan Boddu" <mbo...@bhujji.com>, "Lubomir Sedlar" <lsed...@redhat.com>, 
> "Kevin Fenzi" <ke...@scrye.com>
> Sent: Tuesday, September 17, 2019 5:04:10 PM
> Subject: Re: Add a rule to have a compose when Fedora branched
> 
> On 17. 09. 19 17:00, jkone...@redhat.com wrote:
> > If that is not doable what about taking last Rawhide compose and mark
> > that as first compose of newly branched Fedora? The only thing I'm
> > asking for is to have a base ground which is not available right now.
> 
> That is actually a nice proposal. I wonder whether it is technically
> possible.
> CCing (hopefully) relevant people.
I personally think it should work. As long as the Rawhide compose you take and 
rebrand as F3X
is older than the F3X branching date. That way all the fcs will be fc3x and 
there will not
be any unexpected updated post branch Rawhide packages.

> 
> --
> Miro Hrončok
> --
> Phone: +420777974800
> IRC: mhroncok
> _______________________________________________
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> 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@lists.fedoraproject.org
> 
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org

Reply via email to