> 1) Preferences and all.js. We currently define most of the default
> preferences in /modules/libpref/src/init/all.js. There are things in there
> related to the browser, Necko, gfx, dom, etc. Prety much the kitchen sink.
> 2) Telemetry histograms. They are all defined in
> /toolkit/components/te
On Tuesday 2013-03-19 12:19 +0800, Byron Jones wrote:
> L. David Baron wrote:
> >I'd actually like to see Core higher on the list for the
> >no-canconfirm case. I think it's common for reasonably
> >well-informed Web developers (who would have been able to choose a
> >reasonably correct component
On 3/18/2013 9:27 PM, Jeff Hammel wrote:
> On 03/15/2013 11:33 AM, Gregory Szorc wrote:
>> Our build config has a number of areas where metadata is centrally
>> defined and a module or component's "configuration" is fragmented in
>> the source tree. Here are some examples:
>>
>
>> 3) xpcshell.ini
On 03/15/2013 11:33 AM, Gregory Szorc wrote:
Our build config has a number of areas where metadata is centrally
defined and a module or component's "configuration" is fragmented in
the source tree. Here are some examples:
3) xpcshell.ini master manifest. /testing/xpcshell/xpcshell.ini
defin
Robert Kaiser wrote:
*Ideas for what products we should remove*
And how the XXX should users of those products file new bugs then?
we're talking about removing products from the list of products
initially shown to users, not about removing the products from bmo
completely.
the complete list o
(2013/03/19 2:31), Mark Banner wrote:
On 18/03/2013 16:27, Jason Smith wrote:
- BootToGecko - Big focus at Mozilla with a lot of people working on
this project, so I think this could benefit greatly from being on the
front page.
This should be Firefox OS as that's what the users will know it a
On 3/18/13 10:14 PM, Jason Smith wrote:
Sounds good to me.
Also to add in a piece of private feedback I received - SeaMonkey wants
to remain on the front page as there's a strong community behind it that
still works on that project.
For similar reasons I would like Calendar to stay on the main
We should at least move your suggested removals to the bottom of the new bug
page, given their lower bug filing volume. For instance, SeaMonkey had ~75 bugs
filed in the last month while Firefox for Android (lower on the list) had
closer to 500.
-Alex
On Mar 18, 2013, at 2:14 PM, Jason Smith
Sounds good to me.
Also to add in a piece of private feedback I received - SeaMonkey wants
to remain on the front page as there's a strong community behind it that
still works on that project.
Sincerely,
Jason Smith
Desktop QA Engineer
Mozilla Corporation
https://quality.mozilla.com
On 3/18
Anthony Ricaud schrieb:
I'd suggest renaming Core here. Web developers don't understand what
Core is. They might know Gecko though. Does it make sense to rename Core
to Gecko?
Probably only if we split off anything that Servo doesn't replace into
yet another "Core" product. Yes, Gecko is only
Jason Smith schrieb:
*Ideas for what products we should remove*
And how the XXX should users of those products file new bugs then?
Robert Kaiser
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-plat
On 18/03/13 17:39, L. David Baron wrote:
On Monday 2013-03-18 09:27 -0700, Jason Smith wrote:
I'd actually like to see Core higher on the list for the
no-canconfirm case. I think it's common for reasonably
well-informed Web developers (who would have been able to choose a
reasonably correct comp
On 2013-03-18 12:39 PM, L. David Baron wrote:
I'd actually like to see Core higher on the list for the
no-canconfirm case. I think it's common for reasonably
well-informed Web developers (who would have been able to choose a
reasonably correct component within Core, given the list) to file
stand
Hi all,
Since https://bugzilla.mozilla.org/show_bug.cgi?id=833939 recently landed on
central, I'd like to inform you all of its implications:
* Debug builds no longer write the logs to a file called `console.log` in the
users' AppData directory (for example `~/Library/Application
Support/Fire
I have a concern that removing active community projects would increase the
community/MOCO divide.
Kevin
On Mar 18, 2013 10:35 AM, "Mark Banner" wrote:
> On 18/03/2013 16:27, Jason Smith wrote:
>
>> - BootToGecko - Big focus at Mozilla with a lot of people working on
>> this project, so I think
On 18/03/2013 18:31, Mark Banner wrote:
Mozilla is still committed to providing security and stability updates,
as well as enabling those contributions. We need the bug reports to
enable this to happen, and I think making Thunderbird harder to find
would send the wrong message here.
I wholehear
On 18/03/2013 16:27, Jason Smith wrote:
- BootToGecko - Big focus at Mozilla with a lot of people working on
this project, so I think this could benefit greatly from being on the
front page.
This should be Firefox OS as that's what the users will know it as.
*Rationale for Removals*
- Thunde
On Monday 2013-03-18 09:27 -0700, Jason Smith wrote:
> *existing canconfirm access* *enter bug entry page list*
>
> - Core
> - Firefox
> - Thunderbird
> - Calendar
> - Camino
> - SeaMonkey
> - Firefox for Android
> - Mozilla Localizations
> - Mozilla Labs
> - Mozilla Services
> - Other Products
>
Seems like a good proposal, but dev-platform doesn't really feel like the
best place to get feedback from the people affected. Not sure what would
be, though.
(on Labs: There's a bunch of smaller projects there, but I don't mind if
they're slightly harder to find)
--da
On Mon, Mar 18, 2013 at
Hi Everyone,
In bug 851818 (https://bugzilla.mozilla.org/show_bug.cgi?id=851818),
I've filed a bug to suggest rethinking what our enter bug entry page for
users who are filing bugs with canconfirm or no canconfirm access. I'd
like to discuss what changes we should make to that enter bug entry
Our (ostensibly) weekly DOM bindings meetings continue on Monday March 18th
at 12:30 PM PDT. Note the time change.
Meeting details:
* Monday, March 18, 2012, 12:30 PM PDT (8:30 PM CET)
* Conference room 7-N, San Francisco office, 7th floor.
* Dial-in Info:
- Vidyo room: SFO-7N
- In office or s
testing/crashtests/crashtests.list and layout/reftest/reftest.list are other
examples of a centralized location.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
22 matches
Mail list logo
