Closed
Bug 1011026
(enable-projecteditor)
Opened 10 years ago
Closed 10 years ago
Get ProjectEditor ready to ship in WebIDE
Categories
(DevTools Graveyard :: WebIDE, defect)
DevTools Graveyard
WebIDE
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bgrins, Unassigned)
References
Details
Tracking things that need to be done before enabling itchpad in the new app manager ui
Reporter | ||
Updated•10 years ago
|
Summary: (enable-itchpad) Enable Itchpad In App Manager v2 (pref it on) → Enable Itchpad In App Manager v2 (pref it on)
Reporter | ||
Updated•10 years ago
|
Blocks: enable-webide
Reporter | ||
Updated•10 years ago
|
Summary: Enable Itchpad In App Manager v2 (pref it on) → Enable Itchpad In App Manager v2
Depends on: 1011116
Reporter | ||
Updated•10 years ago
|
Summary: Enable Itchpad In App Manager v2 → Get Itchpad ready to ship in App Manager v2
Reporter | ||
Updated•10 years ago
|
Alias: enable-itchpad → enable-projecteditor
Summary: Get Itchpad ready to ship in App Manager v2 → Get ProjectEditor ready to ship in App Manager v2
Reporter | ||
Updated•10 years ago
|
Reporter | ||
Updated•10 years ago
|
Summary: Get ProjectEditor ready to ship in App Manager v2 → Get ProjectEditor ready to ship in WebIDE
Comment 1•10 years ago
|
||
Brian, we'd like to get this done for 34. Do you think you'll get some time to work on these bugs?
Flags: needinfo?(bgrinstead)
Reporter | ||
Comment 2•10 years ago
|
||
(In reply to Paul Rouget [:paul] (slow to respond. Ping me on IRC) from comment #1)
> Brian, we'd like to get this done for 34. Do you think you'll get some time
> to work on these bugs?
I can work on them, but I doubt I'll be able to knock all of the blockers out myself in this cycle.
The two big tasks here that could take a lot of time being Bug 1011030 (switching to an existing tree implementation), and Bug 1011032 (find and replace plugin). The remaining bugs are pretty small / self-contained.
I think we can probably unblock on bug 1011035 (file drag and drop into tree).
Flags: needinfo?(bgrinstead)
Comment 3•10 years ago
|
||
(In reply to Brian Grinstead [:bgrins] from comment #2)
> I can work on them, but I doubt I'll be able to knock all of the blockers
> out myself in this cycle.
Tell me what I can help with.
> The two big tasks here that could take a lot of time being Bug 1011030
> (switching to an existing tree implementation)
if we just extend the current tree, would that work?
> and Bug 1011032 (find and
> replace plugin). The remaining bugs are pretty small / self-contained.
I don't think it should be a blocker.
> I think we can probably unblock on bug 1011035 (file drag and drop into
> tree).
Ok.
You know better what needs to be done before we hand this tool to developers. Feel free to add/remove bugs to the dependency list, just let me know if you need extra hands to get that fixed for 34.
Reporter | ||
Comment 4•10 years ago
|
||
(In reply to Paul Rouget [:paul] (slow to respond. Ping me on IRC) from comment #3)
> (In reply to Brian Grinstead [:bgrins] from comment #2)
> > I can work on them, but I doubt I'll be able to knock all of the blockers
> > out myself in this cycle.
>
> Tell me what I can help with.
>
> > The two big tasks here that could take a lot of time being Bug 1011030
> > (switching to an existing tree implementation)
>
> if we just extend the current tree, would that work?
>
> > and Bug 1011032 (find and
> > replace plugin). The remaining bugs are pretty small / self-contained.
>
> I don't think it should be a blocker.
>
> > I think we can probably unblock on bug 1011035 (file drag and drop into
> > tree).
>
> Ok.
>
> You know better what needs to be done before we hand this tool to
> developers. Feel free to add/remove bugs to the dependency list, just let me
> know if you need extra hands to get that fixed for 34.
If anyone could pick off any of the blockers (probably besides the file tree item as it is much more involved) I would be happy to review / give an overview of what needs to be done. One in particular I haven't had time to investigate yet is bug 1028240 seems to be an issue maybe with osfile_async_front.jsm.
Updated•10 years ago
|
Whiteboard: [status:inflight]
Updated•10 years ago
|
Whiteboard: [status:inflight]
Hi Brian, I'm looking over my test plan for Firefox 34. Is this still in progress for WebIDE to ship with 34? Thanks!
Flags: needinfo?(bgrinstead)
Reporter | ||
Comment 6•10 years ago
|
||
(In reply to Liz Henry :lizzard from comment #5)
> Hi Brian, I'm looking over my test plan for Firefox 34. Is this still in
> progress for WebIDE to ship with 34? Thanks!
Hi Liz, I'm going to forward this question to Paul.
Flags: needinfo?(bgrinstead) → needinfo?(paul)
(In reply to Liz Henry :lizzard from comment #5)
> Hi Brian, I'm looking over my test plan for Firefox 34. Is this still in
> progress for WebIDE to ship with 34? Thanks!
At this point, we've gotten as far as we're going to get for 34. I'll resolve this bug and remove the few remaining dependencies.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(paul)
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Firefox → DevTools
Updated•5 years ago
|
Product: DevTools → DevTools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•