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
You can use https://wiki.mozilla.org/Firefox/Features/ChannelSwitching/Engagement_Support for more information.
Are we really on-target for 20 deliverables, with time to test, in 4 days?
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.
:malexis, time to close this?
(In reply to Fred Wenzel [:wenzel] from comment #10) > :malexis, time to close this? Indeed.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.