On Thu, 30 May 2019 at 15:32, Miro Hrončok <[email protected]> wrote:

> On 30. 05. 19 20:21, Stephen Gallagher wrote:
> > ## epel8-rawhide:
> > This branch will be left alone until and unless the packager decides
> > that they want to stage a major (possibly incompatible) change for the
> > next RHEL 8.Y minor release. At that time, they will need to remove
> > the package.cfg file from the epel8 branch and manually merge the
> > proposed changes desired into the epel8-rawhide branch and build
> > there.
>
> Just a small consideration here: Can this thing not be called Rawhide?
>
>
Sure. We can colour this master branch whatever colour people want. When
people said EPEL rawhide, it was very clear to everyone in the meeting what
it meant. However you are right it will cause confusion. If you have some
better name we can buy the paint now before the other one dries.



> Rawhide is Fedora. I'd like to keep that clear, so when we talk about
> rawhide in
> various places, we don't have to say: Fedora Rawhide (although we often
> do).
>
> Imagine this conversation:
>
> A: I want to do a major cleanup of %scripts in Fedora.
> B: But what about EPEL?
> A: I'll do it in Rawhide only.
>
> Having an EPEL Rawhide makes the last statement ambiguous.
>
> --
> Miro Hrončok
> --
> Phone: +420777974800
> IRC: mhroncok
> _______________________________________________
> epel-devel mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> 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/[email protected]
>


-- 
Stephen J Smoogen.
_______________________________________________
epel-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]

Reply via email to