Firebug/WeeklyUpdates/2014-11-04: Difference between revisions
< Firebug | WeeklyUpdates
Jump to navigation
Jump to search
No edit summary |
Sebastianz (talk | contribs) (Linked issues) |
||
| Line 41: | Line 41: | ||
* Should issues reported to the Google Code issue tracker be closed when we fixed them for Firebug.next? | * Should issues reported to the Google Code issue tracker be closed when we fixed them for Firebug.next? | ||
** Yes, we want motivate Firebug 2 users use Firebug 3 | ** Yes, we want motivate Firebug 2 users use Firebug 3 | ||
=== Task List === | === Task List === | ||
* Florent: working on test case for Command Editor #143 (Honza: review?) | * Florent: working on test case for Command Editor [https://github.com/firebug/firebug.next/issues/143 Issue #143] (Honza: review?) | ||
* Simon: ? | * Simon: ? | ||
* Honza: Unit tests + Telemetry + PR | * Honza: Unit tests + Telemetry + PR | ||
* Farshid: Properly style Rules side panel [https://github.com/firebug/firebug.next/issues/46 Issue #46] | * Farshid: Properly style Rules side panel [https://github.com/firebug/firebug.next/issues/46 Issue #46] | ||
* Aakash: Style the buttons in the panel contents [https://github.com/firebug/firebug.next/issues/122 Issue #122] + [https://github.com/firebug/firebug.next/issues/155 Issue #155] | * Aakash: Style the buttons in the panel contents [https://github.com/firebug/firebug.next/issues/122 Issue #122] + [https://github.com/firebug/firebug.next/issues/155 Issue #155] | ||
* Sebastian: Headers side panel | * Sebastian: Properly style Headers side panel [https://github.com/firebug/firebug.next/issues/174 Issue #174] | ||
* Djalil: Honza: find an issue (e.g. a test), send an email | * Djalil: Honza: find an issue (e.g. a test), send an email | ||
* Kartik: Properly style console.table() output #136 | * Kartik: Properly style console.table() output [https://github.com/firebug/firebug.next/issues/136 Issue #136] | ||
Latest revision as of 19:28, 4 November 2014
Jan Odvarko, Farshid Beheshti, Sebastian Zartner, Simon Lindholm, Florent Fayolle
Firebug 2
- Firebug 2.0.5 released (promo for Firebug 3 included)
- Honza: report a bug getfirebug.com says 404
- Remove Swarms from getfirebug.com
- Honza: take a look
Firebug 3
- Firebug theme (top priority)
- Get Feedback
- Firebug 3 alpha 1 released
- Current milestone: beta (January 30)
- We need to carefully test Firebug 3 upgrade
- Telemetry
- DOM panel stats
- Server side logging
- Performance.timing
- Selector panel
- Command Editor + all the actions
- Tools (clicking on the button on the toolbar)
- Automated tests
- We need more tests
- Tests are failing (mozilla-download doesn't work)
- Honza: ping Erik
- Immediately revert a commit if it causes test suite failure
- Test bot improvements
- Can we run devtools tests
- Can we run test suite when nightly build is created
- GitHub issue tracker: Assign yourself to an issue when closing it?
- Yes
- Create rules for commit messages
- Always use the issue number in every commit message (if the commit is related to an existing issue).
- We can use existing page for workflow or create new github.com wiki
- Should issues reported to the Google Code issue tracker be closed when we fixed them for Firebug.next?
- Yes, we want motivate Firebug 2 users use Firebug 3
Task List
- Florent: working on test case for Command Editor Issue #143 (Honza: review?)
- Simon: ?
- Honza: Unit tests + Telemetry + PR
- Farshid: Properly style Rules side panel Issue #46
- Aakash: Style the buttons in the panel contents Issue #122 + Issue #155
- Sebastian: Properly style Headers side panel Issue #174
- Djalil: Honza: find an issue (e.g. a test), send an email
- Kartik: Properly style console.table() output Issue #136