#4256 NORM Never A: Killjoy, stable builds

[Zarro Boogs per Child]

#4256: Killjoy, stable builds
---------------------+------------------------------------------------------
  Reporter:  marco   |       Owner:  kimquirk      
      Type:  defect  |      Status:  new           
  Priority:  normal  |   Milestone:  Never Assigned
 Component:  distro  |     Version:                
Resolution:          |    Keywords:                
  Verified:  0       |  
---------------------+------------------------------------------------------
Changes (by cscott):

 * cc: dcbw (added)


Comment:

 I'm content to wait and hear feedback, but do note that I am purposely
 trying to be lazy and avoid reinventing as much as possible.  The current
 joyride system was thrown together as a stopgap because we needed to keep
 making builds.  It's not better.  But hopefully it buys us time to (for
 example) install our own koji instance, or do whatever is "really" needed.

 However, our goal *seems* to be different in part from Red Hat's, in that
 we *don't* want to diverge very much from Red Hat's upstream.  I don't
 want to pull every single package into our own CVS or git or whatever,
 because that would just make synchronizing with Red Hat's upstream much
 harder.  (However, I do want a way to track what changes are coming from
 upstream.)

 So the question is: how can we more effectively manage the subset of
 packages where we have an OLPC-specific fork?  At that (small) scale,
 certain problems may (or may not) become easier.  (And I'd like some
 feedback from people who know koji to better understand how we might
 integrate our koji with Red Hat's koji, if that's the direction we go.)

 I look forward to hearing future ideas and suggestions.

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