Now that we have our initial landing (bug 574217), we need to do the various things we wanted to get done before beta4. Block this bug with appropriate bugs. We should probably triage all of the Tab Candy component, but we can start with any bugs that are dependent on 574217. Also check out Aza's recent "state of Tab Candy" email (from Wednesday night) for other bits.
From the email: A couple specifics: - straightening out themeing issues (move JS-driven CSS to static files, and remaining /content vs /theme splits) - removal of commented out code, "TODO"s without bugs on file - various minor style conventions and formatting nits.
"Tab Candy" is now "TabView" and/or "Tab Sets" ? bug 583044
Mass moving all Tab Candy bugs from Mozilla Labs to Firefox::Tab Candy. Filter the bugmail spam with "tabcandymassmove".
Component: TabCandy → TabCandy
Product: Mozilla Labs → Firefox
Target Milestone: -- → ---
Any status on this? Beta 4 is out and this isn't fixed, so should the fixed bugs be left on this and other bugs block another beta 5 bug? Or perhaps better just use the target milestone and track bugs instead of having this sort of meta bug that needs updating for each milestone.
can someone add bug 590563 ?
I agree with Mardak: let's use target milestones to track bugs for beta releases. Closing this as WONTFIX and removing sub-bugs which have not yet closed.
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.