Re: Copr && Rawhide -- no "rolling updates" workflow

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

 



On Tue, 11 Oct 2016 19:14:34 +0200
Pavel Raiskup <praiskup@xxxxxxxxxx> wrote:

> FYI:
> https://bugzilla.redhat.com/show_bug.cgi?id=1381790
> 
> Seems like the `fedora-rawhide-x86_64` chroot is not going to exist
> from now, which is IMO unnecessary change ... but what could be other
> than those "obvious" consequences for both Copr repo maintainers and
> users? Does this sound like acceptable change?

Well, its a bit confusing actually, but if I understand it right I
guess it should be ok. 

My understanding is that there will no longer be a 'rawhide'
target/repos. Instead right now they will all become 'f26' ones. Then,
when we branch f26, those will follow the branch and new f27 ones will
appear. 

Whats not at all clear is when/if there's going to be any mass adding
the new branch and rebuilding on it, or if that is up to the user? 

Personally, I would say we shouldn't do any mass rebuilding. 
If a project gets to the point where it has no builds for any active
targets we could move it to a 'archive' or just delete it as it would
indicate no one is driving/caring for the software. 

kevin


Attachment: pgpRoYs4PRPdq.pgp
Description: OpenPGP digital signature

_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [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