We should show final cluster reports over all comments submitted over a single beta on our clusters page in separate section below the currently updated ones. Mocks shall be forth coming for some inspiration.
Priority: -- → P2
Target Milestone: --- → 3.0
Summary: Show cluster reports of previous betas → Show cluster reports / themes of previous betas
Let's use the same UI used on /sites where Product type and version can be selected via the comboboxes. The following output should just be a final list of themes over the entire beta. Please take into account of some sanity with those themes are clustered as they're stationary once a new beta is available :).
Assignee: mozaakash → fwenzel
Dave Dash, can you tackle this after your return?
Assignee: fwenzel → dd
This might be a bit of an undertaking, but I can take a look. Currently themes aren't really made to persist, and per-beta clustering might take some computational time (even if they are done only once). Some notes to myself: * add a version field to themes * write a cron to cluster each version * rewrite the existing cron to cluster everything for the current version
Thanks. Keep in mind when writing this that we'll not just cluster beta versions, but versions in general. That'll make this code fit for when we add our release dashboard soon.
Moving this into 3.1. I think you should tackle this one together with bug 623360, which will cluster suggestions for major releases. If you make the code generic, so that it'll cluster all versions (beta or not), and the applicable feedback types separately, we'll be golden.
Target Milestone: 3.0 → 3.1
moving this out of milestone and marking a dependency of the JSON bug.
Depends on: 629019
Target Milestone: 3.1 → ---
Component: Input → General
Product: Webtools → Input
Assignee: dd → nobody
We don't have any of these things in the new Input. Marking this as WONTFIX.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.