Rahul Sundaram wrote:
Josh Boyer wrote:
Look, creating an official Spin is not as simple as "here is my kickstart
file, go build this please."
No, it is not. I have to spend a lot of time, getting that kickstart
file in place first. It isn't a simple matter of running some composes
and calling it a day. There is a heck lot of finicky details to take
care of. Rawhide breaks my compose in subtle ways. You are in rel-eng.
You know the amount of work it takes to get alpha,beta and general
releases out. Are you really asking me to do that work every two weeks
for multiple spins? You can't be serious. This feels more like a
punishment that I have to suffer because other spins broke.
You can't be serious if you're expecting the limited number of Spins SIG
members or Release Engineering members to do that work for you, and
numerous other spins as well.
FWIW though, we have not defined what a spins report should look like
yet. Maybe, just maybe, you have some vague idea of what should be in there?
Kind regards,
Jeroen van Meeuwen
-kanarip
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
