Install Browsershots and make accessible to LP developers
Bug #174422 reported by
Matthew Paul Thomas
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Invalid
|
Low
|
Unassigned | ||
Bug Description
Browsershots <http://
We'll know we are done when a Browsershots installation can be accessed by any Launchpad developer, and instructions for using it have been both (1) announced to the launchpad@ list and (2) recorded on a page that is easily findable from the QualityAssurance area of the Launchpad wiki.
| Changed in launchpad: | |
| assignee: | nobody → matsubara |
| Changed in launchpad: | |
| milestone: | none → 1.2.6 |
| Changed in launchpad: | |
| status: | New → Confirmed |
Revision history for this message
| Joey Stanford (joey) wrote | #1 |
| Changed in launchpad: | |
| importance: | Undecided → Low |
| milestone: | 1.2.6 → none |
Revision history for this message
| Matthew Paul Thomas (mpt) wrote | #2 |
| visibility: | private → public |
| Changed in launchpad: | |
| assignee: | Diogo Matsubara (matsubara) → nobody |
| status: | Triaged → Won't Fix |
| status: | Won't Fix → Invalid |
To post a comment you must log in.
This was partially completed during 1.2.6 however we ran into two problems: 1) hosting unaudited source at Canonical in the DCs and 2) browsershots only deals with public pages and the support for userid/pw has not been added. Therefore we have our own copy but requires an actual person like Diogo to actually run it to test UI changes. Punting to 2.x