2008-10-01
Fedora Spins Process Meeting
Attendees: Mo Duffy (mizmo), Bryan Kearney (bkearney) , Jeroen van
Meeuwen (kanarip), John Poelstra (poelcat), Jesse Keating (f13), Paul
Frields (stickster)
* Everyone was connected to a public gobby session and contributed to
the minutes
== Background ==
https://fedoraproject.org/wiki/Image:Spins-developers-workflow2.png
https://fedoraproject.org/wiki/Websites/Spins <= main wiki page (for
diagrams 'n stuffs)
https://fedoraproject.org/wiki/Websites/Spins/Mockups <= mockup
https://fedoraproject.org/wiki/Image:Spinsfpo-sitemap.png
http://fedoraproject.org/wiki/SIGs/Spins/SpinSubmissionProcess ("former"
spins process)
https://fedoraproject.org/wiki/User:Bkearney/ProposedSpinProcess
(proposed process)
http://git.fedorahosted.org/git/?p=spin-kickstarts.git;a=tree;h=04a876635ff4608f7dc0b9d5780a840f16c4d604;hb=04a876635ff4608f7dc0b9d5780a840f16c4d604
http://spinner.fedoraunity.org/revisor/ (automated "daily" spin creation
no cronjob, started manually)
https://fedoraproject.org/wiki/QA/ReleaseCriteria (spins must meet for
release)
== Meeting Goals ==
1) Know what spins are we composing for Fedora 10
BrOffice
Education-Math
XFCE
Developer
Electronic-Lab
Games
AOS
(Desktop and KDE are part of the main release, not spins)
2) Set forth process to make Fedora 11 run smoothly
== Unanswered Questions (so far) ==
1) How will we track the workflow?
a) custom built tool?
b) wiki pages?
2) How will we track board approval?
3) How will we track trademark approval?
4) Can we create "daily spins"?
a) How often should they be downloadable?
b) How often would people really download them?
5) Can comps.xml be modified for a spin?
6) What flags (checkpoints? approvals?) do we want?
(Requires FESCO document technical requirements and delegate to SPIN Sig \
Board and FESCo does not have technical review)
Spin sig approval
Trademark approval
releng capacity
7) Where have clearly described and explained exactly what a "spin" is?
--can this be done? or is it too complicated?
== Releng Process ==
o Releng will try at Alpha, and Beta--if building spin fails twice,
release engineering will stop trying to build
o Weekly snapshots can be made for torrents, along with weekly snapshots
of other release material.
== Daily Spins ==
o ISOs are not "rsync friendly"
o Spins can be attempted daily, output from the tool and size will be
listed.
== Next Actions ==
1) Jesse looking at kanarip's scripts to build daily spins
2) Kanarip to better document on the wiki "what a spin is"
3)Jon Stanley to collect a list of technical requirements and work with
kanarip to add to a wiki page
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
