[One Mozilla] Test a Small % of Traffic Before a Full Release?

RESOLVED FIXED in 3.7

Status

RESOLVED FIXED
7 years ago
6 years ago

People

(Reporter: christine.brodigan, Unassigned)

Tracking

unspecified
x86
Mac OS X

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

7 years ago
All,

Would it be possible for us to send a small % of traffic to the merged site before going full throttle?

This would allow us a little time to gauge any problems that might occur when the full stream of traffic from mozilla.com and mozilla-europe.org are sent to mozilla.org/firefox and those localized product pages.

It may not be possible, but Steven brought it up today and if it's possible it would be a prudent move indeed!

Add thoughts please!

Comment 1

7 years ago
This is prudent. I'd recommend something like a "soft launch" of 20% of traffic, then rolling out to the rest.
I am not opposed to it at all, but can't currently think of a way how this would be possible with our current (servers and software) setup. Since we run the new setup on the very same servers, they can't serve both the old and new setup at the same time. And if we did something in htaccess like we do for A/B tests, I fear we're compromising the validity of the QA signoff on the merged site, unless we set it up accordingly there first, then re-QA.

But perhaps I am missing something. Can someone from IT weigh in?
(In reply to Fred Wenzel [:wenzel] from comment #2)
> unless we set it up accordingly there first, then re-QA.

By "there" I mean on stage.
CCing oremj for words of wisdom.
(Reporter)

Comment 5

7 years ago
(In reply to Fred Wenzel [:wenzel] from comment #4)
> CCing oremj for words of wisdom.

Fred, thanks for chiming in! If it's not possible, no worries - looks like we'll have a rollback plan ready on deck if things are dire and a design for mozilla.org with dowload capability too.

Jeremy, this is more of a "nice to have" for us, in an attempt to do due diligence :-) 

~cb
(In reply to Fred Wenzel [:wenzel] from comment #2)
> I am not opposed to it at all, but can't currently think of a way how this
> would be possible with our current (servers and software) setup. Since we
> run the new setup on the very same servers, they can't serve both the old
> and new setup at the same time. And if we did something in htaccess like we
> do for A/B tests, I fear we're compromising the validity of the QA signoff
> on the merged site, unless we set it up accordingly there first, then re-QA.
> 
> But perhaps I am missing something. Can someone from IT weigh in?

Sorry, been firefighting all week.

I'm quick to say "not possible today" but this is something we need to work toward (which is akin to how Facebook and others roll out new features).

Fred, let's touch base Mon or Tue.  I'll be in the office.  Need to intro you to a new guy anyway.

Comment 7

7 years ago
I don't know of a good way offhand to do this for the whole thing, but we might be able to do something like this for the redirects from .com -> .org. That is, we might be able to have the redirects trigger for certain IPs, but not most IPs. This would let certain people (like QA) test out the redirects before they go live... not sure we can feasibly do it for a certain percentage of traffic.

We'll want a better solution in the future, but this might be better than nothing for this time.
(Reporter)

Comment 8

7 years ago
Thanks for circling back, closing as resolved, definitely something to work towards in our future:)
Blocks: 610724
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
(Assignee)

Updated

7 years ago
Component: www.mozilla.org/firefox → www.mozilla.org
Product: Websites → Websites
(Assignee)

Updated

6 years ago
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.