contingency plan for the failed-to-build spins/labs?

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

 



So, we have this bug* where some images are failing to be built, and it
happened that the SoaS spin and Design and Jam labs ended up not
succeeding in what became the official release. They aren't release
blocking, so this is fine "by the books", but it seems unfortunate to
miss them due to what's basically a tools bug rather than something
inherently wrong with them.

Obviously they missed the official cut and won't get synced out with
the rest, but I think the download numbers for these are niche enough
that it's probably okay to host them separately.

As I understand it, someone could just keep submitting the builds until
they happen to work, right? (And this might actually provide some
valuable debug info, because we can compare what works and what
doesn't.) Then, we could put those in /pub/alt or something and have
the spins/labs websites link to that. (These could be then signed with
the official key and etc.)

Or, Adam W suggested that we could instead link to nightlies, with a
footnote or something on the websites.



* https://bugzilla.redhat.com/show_bug.cgi?id=1315541


-- 
Matthew Miller
<mattdm@xxxxxxxxxxxxxxxxx>
Fedora Project Leader
--
websites mailing list
websites@xxxxxxxxxxxxxxxxxxxxxxx
https://lists.fedoraproject.org/admin/lists/websites@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora Users]     [Linux ARM]     [ARM Kernel]     [Older Fedora Users]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Devel Java]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Coolkey]     [Yum Users]     [Yosemite News]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]

  Powered by Linux