DevTools/2011-03-23: Difference between revisions
< DevTools
Jump to navigation
Jump to search
m (→Notices) |
No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 9: | Line 9: | ||
* Firefox 4 and Firebug 1.7 shipped! | * Firefox 4 and Firebug 1.7 shipped! | ||
** First new built-in Firefox devtools in a long time | |||
** Web Console screencast | ** Web Console screencast | ||
** DevTools blog | ** [http://blogs.mozilla.com/devtools/ DevTools blog] | ||
*** more activity coming, weekly updates and such | |||
* Firebug update | * Firebug update | ||
** No negative feedback so far | |||
** two blog posts in progress: bigger what's new in Firebug 1.7, changes to page load order between Firefox 3.6 and 4.0 and how you can use Firebug to see this | |||
** Firebug 1.8 | |||
*** going to switch to modules architecture | |||
*** would like to follow the same release cycle as Firefox | |||
*** command line and tab initialization improvements planned | |||
* Firefox.next priorities | * Firefox.next priorities | ||
** See [http://mozilla.github.com/devtools/2011/status.html status page] | |||
** Web Console improvements | ** Web Console improvements | ||
*** docking/undocking | *** docking/undocking | ||
| Line 28: | Line 37: | ||
*** Style Doctor | *** Style Doctor | ||
* Reporting project status here | * Reporting project status here | ||
* Landing code | |||
** Patches need to be killable | |||
** bugfixes and polish probably don't need kill switches | |||
** something like workspaces will need to be able to be preffed out | |||
** the sheriff needs to be consulted for any checkins for the next few days | |||
** land directly on mozilla-central and merge back for these small things | |||
** mechanism for preffing out? | |||
*** makefile variables | |||
*** or have things behind preference existence checks (if (somepref) { do this }) | |||
*** makefile variables have the downside of bad line numbers for exceptions | |||
*** the preferences route is better because it's available in the product to try both paths | |||
*** security problems should probably just be backed out | |||
== Roundtable == | == Roundtable == | ||
Latest revision as of 14:55, 24 March 2011
Meeting Details
- Wednesday Mar. 23, 2010 - 9:00am Pacific, 12:00pm Eastern, 17:00 UTC
- 650-903-0800 or 650-215-1282 x92 Conf# 9364
- 1-800-707-2533 (pin 369) Conf# 9364 (US)
- #devtools on irc.mozilla.org for backchannel
Notices
- Firefox 4 and Firebug 1.7 shipped!
- First new built-in Firefox devtools in a long time
- Web Console screencast
- DevTools blog
- more activity coming, weekly updates and such
- Firebug update
- No negative feedback so far
- two blog posts in progress: bigger what's new in Firebug 1.7, changes to page load order between Firefox 3.6 and 4.0 and how you can use Firebug to see this
- Firebug 1.8
- going to switch to modules architecture
- would like to follow the same release cycle as Firefox
- command line and tab initialization improvements planned
- Firefox.next priorities
- See status page
- Web Console improvements
- docking/undocking
- moving to bottom
- console service
- landing other fixes
- Groundwork for the future
- JSD2
- memory profiling
- Workspaces
- GCLI
- CSS help
- Highlighter
- Style Inspector
- Style Doctor
- Reporting project status here
- Landing code
- Patches need to be killable
- bugfixes and polish probably don't need kill switches
- something like workspaces will need to be able to be preffed out
- the sheriff needs to be consulted for any checkins for the next few days
- land directly on mozilla-central and merge back for these small things
- mechanism for preffing out?
- makefile variables
- or have things behind preference existence checks (if (somepref) { do this })
- makefile variables have the downside of bad line numbers for exceptions
- the preferences route is better because it's available in the product to try both paths
- security problems should probably just be backed out