Changing the way we ship products will require the re-evaluation of many assumptions (see below) and a large shift in the way we think about the size of a "major" release. The criteria for inclusion should be no regressions, well understood effects for users, and completion in time for a planned release vehicle. Again, these serve as proposals and should not be taken as prescriptive:

Firefox 5

Account Manager
Simple Sharing UI
UI Animation
64 Bit on Windows
...anything that improves responsiveness and is ready
...anything that improves stability and is ready
...anything that polishes the user interface and is ready
...anything else serving product priorities and is ready

Firefox 6

Web Applications
FasterCache
OSX 10.7
JS Optimizations
...anything that improves responsiveness and is ready
...anything that improves stability and is ready
...anything that polishes the user interface and is ready
...anything else serving product priorities and is ready

Firefox 7

e10s? deXBLification?
...anything that improves responsiveness and is ready
...anything that improves stability and is ready
...anything that polishes the user interface and is ready
...anything else serving product priorities and is ready

How to ship faster

There's no such thing as a free lunch. To ship smaller bundles of technology more quickly will require us to take a hard look at our existing systems and re-evaluate some of the assumptions we take as immutable, such as:

we must provide binary compatibility for Add-ons
we must support older branches with maintenance fixes
intermittent oranges are unavoidable
scaling localization
we cannot predict the effect of our changes without large scale beta testing
all code needs formal code review
every contributor knows how to obtain code review expediently
every contributor gets equal say on issues of user interface design and technology prioritization

TODO: Process change suggestions (w/Shaver)

https://wiki.mozilla.org/Firefox/Roadmap#Product_Roadmap

_________________

希望不要像 FX4 這樣一拖再拖，已經 beta12 了還沒見 RC 的蹤影。

Simple Sharing UI
e10s
deXBLification
這三個是甚麼意思？

_________________
挑選‧儲存圖片　 History Submenus Ⅱ　 Personal Menu
Page Title in URL Bar　 Double Click Top-Left to Close

Simple Sharing UI我想可能是把F1作為內建吧

..........
不會吧...
越來越多新功能我用不上了。App Tab，Tab Candy 這些新星玩意我現在連碰都不會碰。
看來我快變成不接受新事物的老頭子了, 呵呵

_________________
挑選‧儲存圖片　 History Submenus Ⅱ　 Personal Menu
Page Title in URL Bar　 Double Click Top-Left to Close

難不成Mozilla要走整合的路線？我倒不喜歡這樣，多餘的功能留給附加元件就好

_________________

Simple Sharing UI我猜是類似於FX4 add-on分頁的改變
用分頁形式取代 特化的視窗
--
目前History,Bookmark,Download 還沒有

哦？那不是很簡單嗎？
例如說輸入 chrome://browser/content/places/places.xul, 就能開 Places
外觀方面大有大改，小有小改。像 add-ons 那樣要花上快半年的時間才能定型的 "大工程" 也沒必要吧？
看來工程師都快被 FX4 轟炸死了，這些次要的小玩意也沒時間去搞。

不過，之前有些 mockup 中，Firefox 的選項也換成分頁，附加元件的花巧功能要比現在的多的多。相比起來，現在的 Firefox 4 感覺像內地的山寨東西...

Firefox 4 都還沒出，我已經在期待 Firefox 5 了 。

_________________
挑選‧儲存圖片　 History Submenus Ⅱ　 Personal Menu
Page Title in URL Bar　 Double Click Top-Left to Close

Simple Sharing UI是指F1 這個套件

_________________

嗯嗯嗯
詳細情形可以到這裡
http://f1.mozillamessaging.com/

Firefox 5: Social Sharing, Home Tab, PDF Viewer, Tab Apps

看來Simple Sharing UI可能真的是在說F1