On 10/06/2016 08:55 AM, Miroslav Suchý wrote:
> Hi,
> I want to highlight
>   https://bugzilla.redhat.com/show_bug.cgi?id=1381790
>
> Right now we have rawhide target and when new chroot (e.g. F26) we copy everything from rawhide to F26.
>
> This RFE as for the reverse. I.e. there is no rawhide at all. Rawhide is named F26 and when there is branching of F26 we
> add new chroot named F27.
>
> I would love to hear your comments.

I have a strong opinion against that proposal. IMHO rawhide chroot in
Copr should have fixed name, repo URLs etc. Builds done years ago should
still be available. Other services in Fedora use a similar approach:
PkgDB has "Fedora devel" collection, dist-git has "master" branch, Koji
has "rawhide" repo and build target and so on.  Developers who focus
their development work on rawhide don't even need to know or care about
branching.

Personally, I mostly care about rawhide. Some of my Copr projects that I
still use were created about 2.5 years ago, but they are still
rawhide-only.  It seems like with this proposal I would have to remember
to switch chroots in Copr and fix repo URLs in all the places where I
use them.

What would happen with builds? For me the idea of re-running them, in
correct order, re-bootstrapping, fixing FTBFS etc. sounds a lot like
asking users to move away from Copr to something else (or switch to
using custom-1 chroot with rawhide repos).

--
Mikolaj Izdebski
Software Engineer, Red Hat
IRC: mizdebsk
_______________________________________________
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org