Closed Bug 722399 Opened 12 years ago Closed 12 years ago

Push FF3.6.26 -> FF10.0.1 MU, Advertised

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: akeybl, Assigned: bhearsum)

References

Details

Attachments

(2 files)

mu changes
1.33 KB, patch
nthomas
: review+
armenzg
: checked-in+
Details | Diff | Splinter Review
unthrottle 3.6.26
753 bytes, patch
rail
: review+
bhearsum
: checked-in+
Details | Diff | Splinter Review 
We'll want to push out an unadvertised MU for 3.6.26 -> 10.0 for both the beta and release channels Wednesday 2/1.
Assignee: server-ops-releng → nobody
Component: Server Operations: RelEng → Release Engineering
QA Contact: zandr → release
Assignee: nobody → armenzg
Attached patch mu changes — — Splinter Review 

        Attachment #592832 -
        Flags: review?(nrthomas)

    
  
Blocks: 719214

        Attachment #592832 -
        Flags: review?(nrthomas) → review+

    
    

    
  
(per meeting with akeybl just now) 

Bug#722881 tracks letting FF3.6.26 users who manually check-for-update get MU to FF10.0.

However, bug#722399 is to track enabling the prompted idle-time offering of updates from 3.6.26 to 10.0. This is pending signoff from akeybl. Morphing summary to match reality, and reassigning. Akeybl, please reassign back when ready.
Assignee: armenzg → akeybl
Summary: 3.6.26->10.0 unadvertised MU scheduled for 2/1 → FF3.6.26 -> FF10.0 idle-time advertised MU to FF10.0 (scheduled for 2/1)

    
  
Summary: FF3.6.26 -> FF10.0 idle-time advertised MU to FF10.0 (scheduled for 2/1) → FF3.6.26 -> FF10.0 idle-time advertised MU to FF10.0

    
    

    
  
Whenever you're ready, just push this over to Releng.
Summary: FF3.6.26 -> FF10.0 idle-time advertised MU to FF10.0 → Unthrottle FF3.6.26 -> FF10.0 MU

    
    

    
  
Heads up everybody - we'll likely do this tomorrow (2/14).

For QA verification, we'll want to make sure that https://bugzilla.mozilla.org/show_bug.cgi?id=718685#c9 is the copy offered in the billboard.

    
    

    
  
Shouldn't we update the MU to point at 10.0.1 first?

    
    

    
  
(In reply to Ben Hearsum [:bhearsum] from comment #6)
> Shouldn't we update the MU to point at 10.0.1 first?

Yep - let's use this bug for the unthrottled 3.6.26 -> 10.0.1 MU (which will prompt the user with a billboard). Updating the summary to match.
Summary: Unthrottle FF3.6.26 -> FF10.0 MU → Push FF3.6.26 -> FF10.0.1 MU, Advertised

    
  
Assignee: akeybl → nobody

    
    

    
  


  
Assignee: nobody → bhearsum

        Attachment #597103 -
        Flags: review?(rail)

    
  

        Attachment #597103 -
        Flags: review?(rail) → review+

    
  
Depends on: 727173

    
    

    
  
Comment on attachment 597103 [details] [diff] [review]
unthrottle 3.6.26

W config-dist.php : AUS2_PRODUCTION already exists on version 1.191 : NOT MOVING tag to version 1.192
bhearsum@voot ...aus/xml/inc % cvs tag -F AUS2_PRODUCTION config-dist.php
T config-dist.php

bug 727173 for the push.

        Attachment #597103 -
        Flags: checked-in+

    
    

    
  
Shipped.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering

          You need to log in
          before you can comment on or make changes to this bug.
        






  

    
  







  

    

      
Attachment

      

      
      
      
      
    

    

      

        

          

            
General

            

              Creator: 



            

            
Created: 

            
Updated: 

            
Size: