Closed Bug 646236 Opened 10 years ago Closed 8 years ago

Firefox 5: Rapid Release Tracking Bug

Categories

(mozilla.org Graveyard :: Webdev, task)

All
Other
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: lmesa, Assigned: malexis)

References

Details

Overview: create supporting collateral for mozilla.com to support the rapid release process.

Project Scope: We'll need a reskinned blog that will need to be housed on moz.com/.org
reskinned and designed feedback page (like what we used for fx 4 beta)
reskinned build download page
new copy
new logos
new download buttons
new word marks
1 new newsletter for mercury users

This needs to be ready to go for april 12th deadline, with the feedback page as priority one for the next few dats, followed by the reskinned blog and the remainder of product. 

Dependencies: 
	Legal: n/a
	Security: n/a
	Finance: n/a
	App: n/a
	Other: n/a

Assumptions: Need to be ready for april 12th, with feedback page asap.

Deliverables: design comps for new skinned pages
Depends on: 646868
Depends on: 646870
Depends on: 646876
Depends on: 646880
Depends on: 646881
Depends on: 646889
Depends on: 646896
Depends on: 646911
Depends on: 646914
Depends on: 646916
Depends on: 646920
Depends on: 646942
Depends on: 646943
Depends on: 647241
Depends on: 647242
Depends on: 647678
Depends on: 647896
Depends on: 648001
Depends on: 648002
Depends on: 648011
Group: mozilla-corporation-confidential
Depends on: 648330
Depends on: 648332
Depends on: 648347
Depends on: 648362
Depends on: 648368
Depends on: 648377
Are we really on-target for 20 deliverables, with time to test, in 4 days?
No way...
Maybe Ryan or Austin can help with scheduling.  We could start by asking how long this might all take and figure out a schedule?  How does that sound?
Also wanted to update on timing. Looks like Aurora will go to build on Tuesday, which means we'll actually release pages on Wednesday morning.  Not a huge increase in time, but every little bit helps.
This project just popped up on my radar.  Let's meet early next week to talk about the current status and timing.  

Just to set expectations now, this will not be ready to launch on April 12th.
Okay, just chatted with Laura.  Bug 646870 is the primary bug that needs to roll out for this release.  

We can commit to publishing a static page, in English only, that contains the Aurora download button, and a newsletter signup form.  

Stephen - is QA is available to test this before pushing to production?

We need to set the exact push date / time and get IT on board for the push.

We will define and kick off the remainder of the project the week of April 18th.
(In reply to comment #7)
> Okay, just chatted with Laura.  Bug 646870 is the primary bug that needs to
> roll out for this release.  
> 
> We can commit to publishing a static page, in English only, that contains the
> Aurora download button, and a newsletter signup form.  
> 
> Stephen - is QA is available to test this before pushing to production?

Raymond, will you have this covered?
(In reply to comment #7)

> 
> We need to set the exact push date / time and get IT on board for the push.

We're aiming for Wednesday morning blog post push, but I can't define an exact time.  All we know is that we will go to Build Tuesday afternoon.  We're somewhat at the mercy of build and release engineering to knowing the exact time that buids will be ready

I think that pushing the page live at 8am PDT is fine, and we may announce a little later in the morning or early afternoon.



> 
> We will define and kick off the remainder of the project the week of April
> 18th.

Mike can you invite Grace Jimenez to that meeting.
Depends on: 644517
Depends on: 652121
Depends on: 652124
Depends on: 652249, 652213, 652253
Depends on: 659552
No longer depends on: 659552
:malexis, time to close this?
Flags: needinfo?(malexis)
(In reply to Fred Wenzel [:wenzel] from comment #10)
> :malexis, time to close this?

Indeed.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(malexis)
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.