#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       |  
---------------------+------------------------------------------------------

Comment(by marco):

 Replying to [comment:2 cscott]:
 > I believe this is more a social than a technical problem.  I don't
 expect the build processes to be much different for killjoy, just because
 we don't have time to reinvent the build system *twice* before FRS.  We
 are working on changelogs and package tracking for joyride, which should
 address most of your concerns for killjoy.

 Trying to solve this at the social level, rather than with a very formal
 process, is a very appreciable goal. I'm a little concerned that we
 switched strategy so late in the release process but hey, 1.0 is going to
 be more a start than an end for pretty much everything else...

 > I'd like to see all packages build inside a Koji instance, but I don't
 realistically think that is going to happen before FRS.  If doing so is a
 priority, we should file individual bugs against the 50 or so packages
 which are currently not built inside Koji, and prioritize them
 appropriately.

 To me the requirement for FRS is not to actually build everything in Koji
 but to start going in that direction rather than in the opposite one. Our
 standard answer to people about getting stuff on the builds is "put
 packages in your public_rpms", without a word on how these packages should
 be built. And currently one is actually forced to go out of his way to
 build stuff in koji (see #4252).

 I think most of the packages should always be built into Koji. All the
 Collabora ones for example should. public_rpms is nice to get snapshots
 and experimental packages into the build, but even those should be
 consolidated in Killjoy and built into Koji.

 Right now we are in a pretty weird situation where we forked out the
 olpc-2 branch at some arbitrary point, and we have a bunch of packages of
 unknown provenience and quality on the top it.

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