Following on from the major reorg in July, this bug tracks the second phase, as set out here: https://wiki.mozilla.org/BMO_Reorg_Phase_2 Gerv
Are we going to let people deal with their own queries on this one? The GFX one in particular will be hard to fix accurately.
Let's do what we can, but don't sweat it if it's complicated. Gerv
Ping, can we get this done soon? Its almost 2-months since this was filed, and having the mailnews protocols in a non-comm-central related place is a real pain for bug tracking especially at release time.
As far as I'm concerned, we are good to go. It just requires justdave's time (I presume) to make it happen. Gerv
Increasing severity as not having this done is making it problematic to track mailnews protocol bugs correctly.
justdave: ping? Gerv
Created attachment 358216 [details] transcript of component moves The component moves are all done. Transcript attached. The renames have not been done yet.
Hey Dave: great that you've got most of this done. Any ETA for the rest? Gerv
justdave: ping again? :-) Gerv
When we can expect the remaining work to be done for reorg #2?
Current status: Working from the task summary attached to comment 7, steps 4 and 5 on there are what's left to be done. Step 5 can be done by any bmo admin with component edit rights (timeless typically does that kind of thing in the past). Step 4 needs IT help because it requires shell access for the cleanup script to be run.
Going to try to do step 4 this coming Tuesday night. Not sure who all needs to be warned...
If you can guarantee it's actually going to happen, then post to the relevant newsgroups (l10n/gfx etc.). If you can't, then wait until you've done it before posting - I don't think that's a problem. Gerv
Step 4 is done. Step 5 can be done by anyone with bmo admin privs (timeless, gerv, marcia)
And Step 5 is just bug 451915, right? Thanks very much :-) Gerv