Firebug/WeeklyUpdates/2014-06-24
From MozillaWiki
< Firebug | WeeklyUpdates
Jan Odvarko, Joe Walker, Jakob Kaltenbrunner, Simon Lindholm, Christoph Dorn
Vacations
- Florent: 23 June => 05 July
- Sebastian: till 1st of July
Firebug
- Versioning strategy
- http://semver.org/
- Use <major>.<minor> scheme (just like Firefox)
- Incrementing major number means no back comp
- Incrementing minor number means back comp
- Ideally increase major number every 6 weeks (dot releases would be those done in between the 6 weeks cycle)
- Using the same version number as Firefox makes more sense
- Firebug repo
- Do not branch Firebug 2.0, continue fixes for 2 on the master
- Firebug 3 related stuff goes to Firebug.next
- Later we'll merge 3 into the master (let's see how)
- Firebug 2 issues
- Performance issue, but no test case
- Eval issue
- Issue 7521: Firebug 2.0 nested eval bug
- Issue 7527: Firebug no longer showing dynamically loaded scripts
- Honza: take a look at Simon's suggestion
Firebug.next
- What about wiki for Firebug 3, where to put new pages.
- New installation? But it's more maintenance work (update, plugins, etc.)
- All: any opinions/suggestions?
- File and directory name conventions
- https://github.com/firebug/firebug.next/commit/8ed138c1c2308d18451ef37bc6efa957256eb953#commitcomment-6753048
- Do not use camel case for paths/urls
- Use dashes only for file names
- example: ./helloworld/hello-world-panel.js
- We should always try to have one-word file names.
Demo for London work week, steps towards:
- Firebug theme for native developer tools (design + layout)
- Implementation of basic concepts (side panels, option menus, context menus, search, navigation, panel toolbar, etc.)
- Additional features?
- All: put suggestions into: https://etherpad.mozilla.org/firebug-next
- Christoph, issue list progress
- It should be possible to join: github, code.google and bugzilla issue trackers
- A link will follow