On Wed, 2009-08-05 at 12:58 -0700, Jesse Keating wrote:
> All this really does is create a pseudo rawhide for each release,
> blurring the lines even more around why we even do releases. With a 6
> month cycle, do we really want to take on all this extra headaches and
> hassles just so that you can have some newer experimental software a bit
> sooner, or without doing a wholesale update to the next release?
For fedora-virt folks, we have a "virt-preview" repository, the general
idea being:
- a repo where you can pull f11 builds of the latest rawhide virt bits
- purely for people who want to help with testing f12 virt, but
aren't willing to run rawhide
- it's not about making new features available to f11 users, it's
about allowing f11 users to get involved with f12 development
- if it breaks, you get to keep both pieces - we'll do our best to
fix problems specific to this repo, but in reality we care more
about problems which affect stock f11 or rawhide/f12
- we're trying to keep the limit the packages in the repo to purely
virt related packages - e.g. right now we need something from f12
selinux-policy, but I'm hoping we can get added in an f11 update
rather than pulling in the f12 version and breaking non-virt stuff
It hasn't been around long, but it's working well and we're getting
valuable testing from it. The only thing we're missing is that we can't
add virt-preview packages to the buildroot. We're considering switching
from koji to mock for the builds because of this.
With a little automation, I think this model could work fairly well for
the likes of GNOME.
Cheers,
Mark.
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
