-----BEGIN PGP SIGNED MESSAGE-----
On Tue, 25 Jun 2013 13:32:11 -0400
Bill Nottingham <notting(a)redhat.com> wrote:
(bringing back an old thread)
Dennis Gilmore (dennis(a)ausil.us) said:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> On Sun, 12 May 2013 17:56:20 +0200
> Christoph Wickert <christoph.wickert(a)gmail.com> wrote:
> > Hi,
> > back in April we discussed the F19 spins and it was widely agreed
> > that http://fedoraproject.org/wiki/Releases/19/Spins
> > canonical list of approved spins that need to be produced.
> > However this doesn't seem to be the case, I only see the desktop
> > spins. In fact, that is not even true given that I cannot find
> > MATE either.
> > What does the spins SIG need to do in order to get the remaining
> > spins?
> We have for the last few releases composed the 5 main desktop spins
> Gnome, KDE, LXDE, XFCE and SoaS for Alpha and Beta and in theory
> nightlies have been used for QA. before making the 5 we only made
> KDE and Gnome. QA has not been really happening as is evidenced by
> spins regularly failing to compose, and being shipped DOA, as in the
> design-Suite in F18 and Games being dropped for failing to compose.
> I personally fixed a bunch of spins in F17.
> For Fedora 19 I'm planning to only compose those 5 for GA also and I
> will only be shipping them if they have been tested and signed off
> by at least 3 people as working. This is due to Spins having been
> shipped broken in the past. I think we need to stop pretending
> there is a spins SIG as its not been functional or working for a
> few years.
Functional or not, has this been widely disseminated?
- Are all the spin maintainers aware?
- Is the websites team that builds and maintains spins.fp.o aware, and
ready to handle only updating some of the spins listed there?
- Is it in the release notes?
It's a very large change to drop five deliverables, obviously.
websites are aware, spin maintainers were notified via the spins list,
no objections have been raised. not sure if its in the release notes.
> Perhaps the question we really need to ask is how should we deploy
> and install Fedora, Which is not something we can change or solve
> for f19 or probably even f20. An idea that comes to mind is to
> have package selections and post install config tasks ship as
> kickstart snippets with the DVD. we then use grub/syslinux to
> present a menu to the users to have different frameworks that
> resemble the spins the kickstart is fed to anaconda then at boot
> time or anaconda gives you the option to select them.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.19 (GNU/Linux)
> -----END PGP SIGNATURE-----
> spins mailing list
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
-----END PGP SIGNATURE-----