#7528 HIGH 8.2.0 (: Firmware release - 5.110.22.p17

[Zarro Boogs per Child]

#7528: Firmware release - 5.110.22.p17
-----------------------------+----------------------------------------------
   Reporter:  carrano        |       Owner:  carrano             
       Type:  defect         |      Status:  new                 
   Priority:  high           |   Milestone:  8.2.0 (was Update.2)
  Component:  wireless       |     Version:  not specified       
 Resolution:                 |    Keywords:                      
Next_action:  test in build  |    Verified:  0                   
  Blockedby:                 |    Blocking:                      
-----------------------------+----------------------------------------------

Comment(by carrano):

 Replying to [comment:9 cscott]:
 > Please reassign this bug to someone who is charged with doing the
 testing, then.  My part of this bug is over.

 That would be me. I forgot to put it back to me, thank you for doing that.

 >
 > Also: is this firmware release process you describe documented anywhere?
 This is the first I've heard of it.

 I'm surprised to read that because it all started with your idea:
 {{{
 ---------- Forwarded message ----------
 From: C. Scott Ananian <cscott at laptop.org>
 Date: Fri, Mar 14, 2008 at 11:45 PM
 Subject: Re: wireless firmware 5.110.22.p6
 To: Michail Bletsas <mbletsas at laptop.org>
 Cc: techteam at laptop.org, dennis at laptop.org


 On Fri, Mar 14, 2008 at 10:30 PM, Michail Bletsas <mbletsas at laptop.org>
 wrote:
 >
 > FW release W8388-5.110.22.p6

 Have we set up a process for ensuring new wireless firmware get into
 the build yet?  A good start would be filing a trac bug -- and
 assigning to Dennis, I think, who maintains the RPM packaging.  We'd
 probably want this new firmware to age some in joyride, and it
 probably makes sense to start that aging process as soon as possible.
  --scott
 }}}

 It was then discussed with all the involved (I'm sure some pipemail
 research will reveal that). After some months the subject was discussed
 again. Please check Michael 's comments on that, (you were cc'd):

 {{{
 from    Michael Stone <michael at laptop.org>
 to      Ricardo Carrano <carrano at laptop.org>
 cc      John Watlington <wad at laptop.org>,
 Kim Quirk <kim at laptop.org>,
 Michail Bletsas <mbletsas at laptop.org>,
 Jim Gettys <jg at laptop.org>,
 Chris Ball <cjb at laptop.org>,
 "C. Scott Ananian" <cscott at laptop.org>,
 Javier Cardona <javier at cozybit.com>
 date    Thu, Apr 10, 2008 at 4:05 PM
 subject Re: wireless firmware update



 On Thu, Apr 10, 2008 at 03:15:28PM -0300, Ricardo Carrano wrote:
 > And the truth is that the current process is public and documented (for
 > instance there is a lot of on going discussion on the 22.p9 fw - please
 > refer to #6869).

 Making a ticket to track the inclusion of the package into builds is
 perfectly appropriate and I have been watching #6869 with interest.

 > Yes, I insist: there is a process. And its ticket based, and the
 > instructions were: once it is ready to joyride, we assign the ticket
 > to dgilmore. If I got it wrong I appreciate if someone points me to
 > the correct direction.

 Dennis comes into the picture during periods of change control which
 occur during periods of motion towards a stable release. During periods
 of unstable development, nothing more than notification is required in
 order to change the build. Also, OLPC has no present intentions to
 further change candidate-703 before making it official-703. This means
 that we are at the very beginning of a period of unstable development.

 In short, please advertise new wireless firmware blobs and insert them
 into Joyride at will until we announce the resumption of change control
 in preparation for our next release. This behavior will result in an
 appropriate version of your new wireless firmware being included in our
 next release with high probability.

 [...removed unrelated part...]

 Yours,

 Michael
 }}}


 >I was specifically asked by m_stone to add this firmware to joyride.  Was
 he wrong to do so?

 I think I already commented on that.

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