Fedora Spins Process Meeting 2008-10-01

John Poelstra poelstra at redhat.com
Thu Oct 2 04:27:16 UTC 2008

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/Websites/Spins <= main wiki page (for 
diagrams 'n stuffs)
https://fedoraproject.org/wiki/Websites/Spins/Mockups <= mockup
http://fedoraproject.org/wiki/SIGs/Spins/SpinSubmissionProcess ("former" 
spins process)
(proposed process)
http://spinner.fedoraunity.org/revisor/ (automated "daily" spin creation 
no cronjob, started manually)
https://fedoraproject.org/wiki/QA/ReleaseCriteria (spins must meet for 

== Meeting Goals ==
1) Know what spins are we composing for Fedora 10
   (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 

== 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

More information about the fedora-devel-list mailing list