Closed Bug 652124 Opened 14 years ago Closed 14 years ago

[Rapid Release] Make first run page link to the "fake" beta a blog post

Categories

(www.mozilla.org :: General, defect, P1)

Product:
www.mozilla.org
Component:
General
Version:
Firefox 5
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: lmesa, Assigned: sgarrity)

References

Details

We're creating a fake beta to help us test the channel switcher. We want the first run of this build to be a blog post, likely a specific post on dev planning explaining the channel switcher and asking the user to change their channel back to Aurora and give feedback about their experience. This blog post will likely be written my christian and engagement. This post should be ready to go 4/28
hi all. this bug is currently not assigned to anyone. who should we assign this bug to? Just want to make sure this bug is assigned to someone and make sure we meet the 4/28 timing. we hope to have the blog by this Tuesday, 4/26 please let us know if you need additional info. thanks!
Assigning to Christian, but the PMMs will provide the first draft on Monday. and adding Erica
Assignee: nobody → clegnitto
Assignee: clegnitto → nobody
Component: General → www.mozilla.com
OS: Mac OS X → All
Product: Firefox → Websites
QA Contact: general → www-mozilla-com
Hardware: x86 → All
Target Milestone: --- → 2.3
Version: unspecified → Firefox 5
Priority: -- → P1
Summary: Make first run of the "fake" beta a blog link → [Rapid Release] Make first run page link to the "fake" beta a blog post
Hi all. Quick Update. We will be generating "fake/realbeta1" update to earlier Fx4.0 beta users (en only). The "fake/realbeta1" is a aurora build branded beta to test our channel switcher. This is happening tomorrow or Friday. Christian is writing a detailed blog post on this process. To explain this fun and exciting process to our Fx4.0 beta users, we would like the first run page to link to Christian's blog post (not the standard first run page). Link to the blog is TBD. Christian, I believe you already have a draft. Would you be able to send us the link to this blog so we can update this first run page. Slater/StevenG, please let me know if you have any question regarding this process. I have marked it as a 2.3 milestone, however, this will go out in a out-of-cycle milestone (tomorrow 4/28 or Friday 4/29).
Assignee: nobody → steven
Severity: normal → critical
Grace, per our hallway convo please let us know when you have the URL for the fake first run page as well as the blog post it should redirect to. Basic outcome we want: people who download this "fake" beta are redirected to Christian's blog post. (Which isn't quite the same as the first run page linking to the blog post, as noted in comment #3.)
(In reply to comment #4) > Grace, per our hallway convo please let us know when you have the URL for the > fake first run page as well as the blog post it should redirect to. thanks slater. will provide the links as soon as i have them. > > Basic outcome we want: people who download this "fake" beta are redirected to > Christian's blog post. (Which isn't quite the same as the first run page > linking to the blog post, as noted in comment #3.) - yes.
hi all, Here is the first run link we are using: http://www.mozilla.com/en-US/firefox/5.0/firstrun/ Blog link: TBD.
I'm not clear what we need to do here. Can someone clarify what needs to be built?
(In reply to comment #7) > I'm not clear what we need to do here. Can someone clarify what needs to be > built? hi steven. we just need to redirect this link: http://www.mozilla.com/en-US/firefox/5.0/firstrun/ to a blog post link. im still waiting for the blog post link and will provide as soon as i get it.
Grace, shouldn't the link be http://www.mozilla.com/en-US/firefox/5.0b1/firstrun/? That's the naming convention we've used in the past - the one you're suggesting should be used for the main Fx5 GA first run page (which we definitely don't want pointing to a personal blog post). Please confirm, but this really doesn't seem right to me.
(In reply to comment #9) > Grace, shouldn't the link be > http://www.mozilla.com/en-US/firefox/5.0b1/firstrun/? That's the naming > convention we've used in the past - the one you're suggesting should be used > for the main Fx5 GA first run page (which we definitely don't want pointing to > a personal blog post). > > Please confirm, but this really doesn't seem right to me. Discussed with Rel Eng and the correct link is what grace has in comment 8. I agree it doesnt confirm to past conventions, but this is being done in part to "reduce importance of explicit beta versions" plan.
Ok, so who's in charge of making sure we change it back later? This all seems like unnecessary extra work to me.
We will be responsible for filing a bug to redirect this link back to WN/FR page once we have a "real beta" on may 17th, but the URL convention, from what john o'duinn said, will now remain with what grace has in comment 8, or below: http://www.mozilla.com/en-US/firefox/5.0/firstrun/ http://www.mozilla.com/en-US/firefox/5.0/whatsnew/ My understanding is that from now on, we wont be adding b1 etc to end of urls, but just changing 5.0 to 6.0, etc.
(In reply to comment #8) > (In reply to comment #7) > > I'm not clear what we need to do here. Can someone clarify what needs to be > > built? > > hi steven. we just need to redirect this link: > http://www.mozilla.com/en-US/firefox/5.0/firstrun/ to a blog post link. im > still waiting for the blog post link and will provide as soon as i get it. Link to blog will be: http://developer.mozilla.org/devnews/index.php/2011/04/28/beta-channel-switcher-testing
I am. This is the consequence of how the builds identify themselves. Think of the betas in the new world more like past RCs than betas. We need the beta builds to identify how final does and the url loaded is based off that version (see http://mozilla.github.com/process-releases/draft/development_specifics/#versioning-firefox)
(In reply to comment #12) > We will be responsible for filing a bug to redirect this link back to WN/FR > page once we have a "real beta" on may 17th, but the URL convention, from what > john o'duinn said, will now remain with what grace has in comment 8, or below: > > http://www.mozilla.com/en-US/firefox/5.0/firstrun/ > http://www.mozilla.com/en-US/firefox/5.0/whatsnew/ > > My understanding is that from now on, we wont be adding b1 etc to end of urls, > but just changing 5.0 to 6.0, etc. Quick question, given the naming convention for these URLs, will we also have an end of life and/or redirect policy for these pages? -CB
What do you mean? When we EOL a build, I put in a redirect to a generic out-of-date page...see: http://www.mozilla.com/en-US/firefox/3.0/firstrun/ http://www.mozilla.com/en-US/firefox/3.0/whatsnew/
(In reply to comment #16) > What do you mean? When we EOL a build, I put in a redirect to a generic > out-of-date page...see: > http://www.mozilla.com/en-US/firefox/3.0/firstrun/ > http://www.mozilla.com/en-US/firefox/3.0/whatsnew/ Christian, perfect! that's what I was looking for (sorry, still new to how things work) & wanting to avoid situations like http://www.mozilla.com/en-US/firefox/video/?video=performance-3.5 - which is actually a video promoting Firefox 4 (argh!)
Update on timing--we should prepare for a push tomorrow, not today.
I didn't mean to sound snippy, just wanted to clarify if what I was talking about was what you were talking about :-)
Timing update--Monday is now the earliest we will push.
I can confirm for you within the hour. I want to double check.
The correct link is indeed:http://developer.mozilla.org/devnews/index.php/2011/04/28/beta-channel-switcher-testing/ However, just wanted to double check something-- From https://bugzilla.mozilla.org/show_bug.cgi?id=653636#c23 it looks like https...not sure if that matters?
Just spoke with John O'Duinn about the page. If you're testing and expecting to see the blog post page, you won't because we haven't pushed it live. That will be one of the last steps before we can consider this beta "launched". What we can check, however, is the url of the page rel eng is testing, before the redirect goes to http://developer.mozilla.org/devnews/index.php/2011/04/28/beta-channel-switcher-testing/. I have that redirect as http://www.mozilla.com/en-US/firefox/5.0beta/details/
I think comment #24 and #25 are referring to something else. That's the billboard that appears in the update dialog within the app. The earlier comments in this bug are talking about the pages that are loaded by the app *after* the update is applied. In short, I believe comment #21 is correct.
Ok, cool. So we're good to go?
Not sure who you are asking, but from me its a "please go ahead and set up the redirects described in comment #21".
Steven--please go ahead and do this ASAP.
This needs to be live tomorrow morning.
Severity: critical → blocker
Is this for en-US only?
Yes, it is. Thanks Steven.
Done in trunk for en-US in r88183. Merged to stage in r88184.
Status: NEW → RESOLVED
Closed: 14 years ago
Keywords: qawanted
Resolution: --- → FIXED
This redirect wasn't supposed to be /details/ - it was supposed to be firstrun|whatsnew. Fixed in trunk in r88194 and r88197. Merged to stage in r88198.
Mixed up URLs again. Sorry for all the bugspam. I was redirecting 5.0beta/firstrun - should just be 5.0/firstrun. Fixed in trunk in r88202. Merged to stage in r88203.
same for firstrun pages too
That is expected--its expected because we haven't pushed the blog post live, and we can't push the blog live until we're about to push 5.01b live. So, basically, I think the test it to see that we got the redirect to the 404, and we did--so I would say this is actually working as expected.
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
Whiteboard: push needed
Keywords: push-needed
Whiteboard: push needed
pushed to production r88219
Keywords: push-needed
Component: www.mozilla.org/firefox → www.mozilla.org
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.