1080705 - differentiate between product and temporary branches of the product

Status: RESOLVED WONTFIX

(Input Graveyard :: Submission, defect)

Description

[Will Kahn-Greene [:willkg] ET needinfo? me]

Periodically, a group will branch a product and do a temporary channel that has some set of changes in it that need to be tested more thoroughly. For example, there have been UX builds like what we did for Australis. If those builds want to gather feedback separately, there's no good way for them to denote that they are builds of a different branch.

One idea to solve this would be to add a "build" or "branch" column to the feedback_response table. We would populate this column from a corresponding field. For the forms we host, that'd come in a querystring param. For the Input API, it'd just be another value.

For example:

Some group really wants to do a version of Firefox where the default theme is very pink. They branch Firefox mainline and create a channel of pink Firefox so as to do user testing to prove it's superior.

In the product, they'd change the feedback url to this:

   https://input.mozilla.org/%LOCALE%/feedback/%APP%/%VERSION%/?build=pink


This bug covers figuring out the implementation details and implementing them.

Comment 1

[Will Kahn-Greene [:willkg] ET needinfo? me]

Bumping this to 2015q1 because we're out of time for this quarter.

Comment 2

[Will Kahn-Greene [:willkg] ET needinfo? me]

I'm pushing this off until we have an actual need for it figuring we'll have more information with which to make a good architectural decision at that point.

Comment 3

[Will Kahn-Greene [:willkg] ET needinfo? me]

This issue never came up again. Given that, I'm going to WONTFIX it.