#5565 BLOC Update.: Policy for deployment of new OFW releases

[Zarro Boogs per Child]

#5565: Policy for deployment of new OFW releases
--------------------------------+-------------------------------------------
  Reporter:  wmb at firmworks.com  |       Owner:  jg      
      Type:  enhancement        |      Status:  new     
  Priority:  blocker            |   Milestone:  Update.2
 Component:  distro             |     Version:          
Resolution:                     |    Keywords:          
  Verified:  0                  |  
--------------------------------+-------------------------------------------
Changes (by jg):

 * cc: dgilmore, rsmith, wmb at laptop.org, cscott, cjb (added)
  * priority:  normal => blocker
  * type:  defect => enhancement
  * component:  new component => distro
  * milestone:  Never Assigned => Update.2


Comment:

 I concur.  Mitch, Richard, please update

 http://wiki.laptop.org/go/Firmware_release_procedures

 to reflect current practice.  One of the procedural steps must be to
 inform Dennis (our release tzar) of the new firmware (though this could be
 piggybacked on the mail to the ECO list, I suspect).
 Dennis, are you on the ECO mailing list?

 Who has the action item to produce the bootfw.zip file for 653, since did
 not "do the right thing"?

 Dennis; you are also the gatekeeper to the build; when you are informed of
 new released firmware, it may be that you can act as QC to ensure nothing
 got missed in the release of the firmware.

 We also need to codify our OS release procedures as well, in a similar
 document.  That is the subject of #5599.

-- 
Ticket URL: <http://dev.laptop.org/ticket/5565#comment:1>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system