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

Comment(by cscott):

 I disagree.  I do not think we should be encouraging people to do
 independent upgrades of their firmware at the present time.  Firmware
 should be coupled with an OS build it is known to work with.  We've got
 enough update paths at the present, adding one more (untested) one is just
 going to multiply our problems.

 If you have a developer key, you can upgrade to the q2dxx.rom image as
 usual.  That's fine.

 If you don't have a developer key, you should get the new firmware when
 you upgrade to a new build.  Having a signed bootfw.zip file is a nice
 fallback if we need it, but it should not be the recommended firmware
 upgrade procedure.

 Getting new firmware into new builds is Dennis' job, and that should be
 completely decoupled from the ECO procedure, which is about taking builds,
 once made, and "signing off" on their use by Quanta.

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