#4256 NORM Never A: Killjoy, stable builds

[Zarro Boogs per Child]

#4256: Killjoy, stable builds
--------------------+-------------------------------------------------------
 Reporter:  marco   |       Owner:  jg            
     Type:  defect  |      Status:  new           
 Priority:  normal  |   Milestone:  Never Assigned
Component:  distro  |     Version:                
 Keywords:          |    Verified:  0             
--------------------+-------------------------------------------------------
 While I love the experimentation which is going on with joyride, I think
 we need to come up with a process for stable builds asap.

 According to the roadmap, we are two weeks away from the 1.0 code freeze.
 The infrastructure and the process needs to be working well at least a few
 days before the freeze, so that we have time to get the new packages in
 it.

 I think some of the killjoy requirements are different then joyride.
 Anyway these are what I consider the more urgent to address:

  * We should keep strong editorial control on what goes inside the
 distribution.
  * All the packages that goes into the build should either built into the
 Fedora build system or be content/activity bundles.
  * During code freeze all the changes should be approved.
  * We need to make the process more transparent. The testing team, for
 example, needs to know what is going into the builds and when. Unlike
 joyride I don't think we will want hourly builds.

-- 
Ticket URL: <https://dev.laptop.org/ticket/4256>
One Laptop Per Child <https://dev.laptop.org>
OLPC bug tracking system