Re: Intent to disable service workers and push in 52 ESR

We disabled some features (iirc Hello and Pocket) in ESR45. The preference is to keep ESR inline with what's in the mainline release but we're also supporting ESR on a best effort basis. I think the rationale in this thread for disabling service workers and push in ESR52 makes sense if we're not go

Re: Sheriff Highlights and Summary in February 2017

Hi Tomcat, Do you have any more details about the reasons why the 297 changesets needed to be backed out? Thanks, Lawrence On Wed, Mar 1, 2017 at 6:05 AM, Carsten Book wrote: > Hi, > > We will be more active in 2017 and inform more about whats happening in > Sheriffing and since its already M

Re: Sheriff Highlights and Summary in February 2017

ut rate in the past i think - so it stabilized > now with this 6-7 % backout rate in the last months, > > If you think its useful, i can provide for the next monthly report a more > detailed analysis like x % = backouts because builds bustages, y %= > backouts for test failures et

Re: unowned module: Firefox::New Tab Page, help me find an owner

On Wed, Mar 22, 2017 at 10:33 AM, Ben Kelly wrote: > On Wed, Mar 22, 2017 at 10:00 AM, David Burns wrote: > > > On 22 March 2017 at 13:49, Ben Kelly wrote: > > > >> Finding someone to own the feature and investigate intermittents is > >> important too, but that doesn't mean the tests have zero

Re: switch to macosx cross-compiled builds on taskcluster on trunk

\o/ Congratulations to everyone involved in making this happen! (Take a breath.) On to release! On Thu, Jun 22, 2017 at 3:09 PM, Kim Moir wrote: > After successful testing this morning, we have now enabled macosx nightly > updates again. > > The migration is complete, enjoy your cross compiled b

Re: [RelEng] Switching to TaskCluster Windows builds on Wednesday July 26th

What Dustin said. Thrilled to see some big jobs moving to TC. Keep pushing! Lawrence On Fri, Jul 21, 2017 at 3:02 PM, Dustin Mitchell wrote: > Nice work -- what a milestone! > > Dustin > ___ > release-engineering mailing list > release-engineer...@lis

Re: [RelEng] Switching to TaskCluster Windows builds on Wednesday July 26th

w00t! Well done! On Thu, Jul 27, 2017 at 11:52 AM, Justin Wood wrote: > And with that, new Nightly updates are live to 100% of our userbase. > > Thank you again! > ~Justin Wood (Callek) > > On Wed, Jul 26, 2017 at 9:17 PM, Justin Wood wrote: > > > As of now we are declaring this work a success!

New: QA Test Plan Sign-off Requirement

(cross posting to a few lists for visibility) tl;dr Starting with the Firefox 57 release, test plans will require sign-off from Engineering, Product and QA before testing begins. Engineering, Product, and QA each have unique insights into risks associated with feature development. We have the be

Re: Sheriffing Newsletter September!

> 1. Ryan's last week as Sheriff! > > As you might have heard that RyanVM is leaving the Sheriff Team to he will > be leading a new quality team as part of the Firefox org. So its his last > week as Sheriff this week. > Thanks for all what do you did for keeping the Trees open and making the > Sher

Re: Decommissioning "dumbmake"

On Sun, Oct 18, 2015 at 7:14 PM, Nicholas Nethercote wrote: > On Sun, Oct 18, 2015 at 3:12 PM, Eric Rescorla wrote: > > > > What's needed here is a dependency management system that > > simply builds what's needed regardless of what's changed, > > Otherwise known as "a proper build system". glan

Re: Thanks for all the great teamwork with the Sheriffs in 2015!

hear, hear! Thank you. Lawrence On Wed, Dec 30, 2015 at 9:27 AM, Kartikaya Gupta wrote: > Yes, thank you to all the sheriffs for all their hard work! > > On Wed, Dec 30, 2015 at 9:19 AM, Carsten Book wrote: > > Hi, > > > > Sheriffing is not just about Checkins, Uplifts and Backouts - its also

Re: Intent to ship: Support for color-adjust CSS property

Whether or not we ship with the feature enabled, the ability to disable a feature with a pref gives us an easy out if a critical issue is discovered. (For ex, a code path that results in a top crash.) I suggest that we create the pref in either case and plan to remove it after a couple of releases

Re: Intent to deprecate: MacOS 10.6-10.8 support

On Sat, Mar 12, 2016 at 4:46 PM, Kyle Huey wrote: > On Fri, Mar 11, 2016 at 4:28 PM, Terrence Cole wrote: > > > We need to drop support for OSX 10.8 and Windows Vista yesterday, not > next > > year. We need to cut our losses and ship E10S while we're still relevant. > > We need to be the browser

Re: Triage Plan for Firefox Components

Softvision also makes use of the feature keyword as one way to identify new feature work to test in upcoming releases. Lawrence On Thu, Mar 31, 2016 at 10:49 AM, Milan Sreckovic wrote: > We do have a feature keyword today. While it may be most used for the > documentation purposes, the feedbac

Re: Triage Plan for Firefox Components

On Fri, Apr 1, 2016 at 9:30 AM, Lawrence Mandel wrote: > On Fri, Apr 1, 2016 at 8:17 AM, Kartikaya Gupta > wrote: > >> It seems to me that when this bug program was started, it had these >> two goals (quoted from Emma's previous email): >> >> "First,

Re: Triage Plan for Firefox Components

On Fri, Apr 1, 2016 at 8:17 AM, Kartikaya Gupta wrote: > It seems to me that when this bug program was started, it had these > two goals (quoted from Emma's previous email): > > "First, we want > to make better assertions about the quality of our releases by making clear > decisions about which b

Re: Intent to deprecate: MacOS 10.6-10.8 support

On Fri, Apr 1, 2016 at 11:48 AM, wrote: > On Thursday, March 10, 2016 at 12:04:03 PM UTC-6, Benjamin Smedberg wrote: > > This is notice of an intent to deprecate support within Firefox for the > > following old versions of MacOS: 10.6, 10.7, and 10.8 > > > > The motivation for this change is that

Re: [Bug 1224726] High memory consumption when opening and searching a large Javascript file in debugger.

Good intentions or not, we need to stop this activity. Mark - What's our usual approach to address bug spam? Lawrence On Monday, 11 April 2016, Mats Palmgren wrote: > On 2016-04-11 23:32, Emma Humphries wrote: > >> Here's the open bugs they have touched http://mzl.la/1Q3w24o >> > > He touched

Re: [Bug 1224726] High memory consumption when opening and searching a large Javascript file in debugger.

On Monday, 11 April 2016, Mike Taylor wrote: > On 4/11/16 5:04 PM, Mats Palmgren wrote: > >> He touched 283 bugs in the last 48 hours, most of which are FIXED. >> > > If anyone in the QA org reads this list, maybe they could reach out and > teach him how to more effectively contribute? > > (I see

Re: Moving XP to ESR?

On Mon, Apr 18, 2016 at 9:04 AM, Henri Sivonen wrote: > XP has now gone for two years without security patches from Microsoft. > Additionally, as of its latest release, Chrome no longer supports XP. > > When 46 ships, it would be a great time to make AUS advertise 45 ESR > builds to XP (even on n

Re: Intent to deprecate: MacOS 10.6-10.8 support

Hi Kohei, I had planned to update the thread after the post went live so that I had the link. Thank you for posting it. Lawrence On Sat, Apr 30, 2016 at 12:38 AM, Kohei Yoshino wrote: > Today's announcement from Mozilla: > > https://blog.mozilla.org/futurereleases/2016/04/29/update-on-firefox-

Re: Intent to deprecate: MacOS 10.6-10.8 support

On Sat, Apr 30, 2016 at 1:37 AM, Mike Hommey wrote: > On Sat, Apr 30, 2016 at 12:38:37AM -0400, Kohei Yoshino wrote: > > Today's announcement from Mozilla: > > > https://blog.mozilla.org/futurereleases/2016/04/29/update-on-firefox-support-for-os-x/ > > > > The decision is fine but why don't they

Re: Intent to deprecate: MacOS 10.6-10.8 support

On Mon, May 2, 2016 at 2:28 PM, Ralph Giles wrote: > On Fri, Apr 29, 2016 at 9:52 PM, Lawrence Mandel > wrote: > > > I had planned to update the thread after the post went live so that I had > > the link. Thank you for posting it. > > The blog post just says &

Re: Intent to deprecate: MacOS 10.6-10.8 support

On Tue, May 3, 2016 at 6:56 PM, Mike Hommey wrote: > On Tue, May 03, 2016 at 05:18:17PM -0500, Adam Roach wrote: > > On 5/3/16 4:59 PM, Justin Dolske wrote: > > > On 5/3/16 12:21 PM, Gregory Szorc wrote: > > > > > > > * The update server has been reconfigured to not serve Nightly > > > > updates

Re: Intent to deprecate: MacOS 10.6-10.8 support

On Tue, May 3, 2016 at 11:11 PM, Xidorn Quan wrote: > On Wed, May 4, 2016 at 9:46 AM, Lawrence Mandel > wrote: > >> On Tue, May 3, 2016 at 6:56 PM, Mike Hommey wrote: >> >> > On Tue, May 03, 2016 at 05:18:17PM -0500, Adam Roach wrote: >> > > On 5/3/16

Re: Reverting to VS2013 on central and aurora

On Tue, May 10, 2016 at 7:05 PM, Ehsan Akhgari wrote: > On 2016-05-10 4:45 PM, Gregory Szorc wrote: > > On Thu, May 5, 2016 at 9:26 PM, Gregory Szorc wrote: > > > >> There is a compiler bug in VS2015 that results in SSE instructions being > >> emitted when they shouldn't be. Since Firefox still

Re: Reverting to VS2013 on central and aurora

On Tue, May 10, 2016 at 7:29 PM, Xidorn Quan wrote: > On Wed, May 11, 2016 at 6:45 AM, Gregory Szorc wrote: > > > On Thu, May 5, 2016 at 9:26 PM, Gregory Szorc wrote: > > > > > There is a compiler bug in VS2015 that results in SSE instructions > being > > > emitted when they shouldn't be. Since

Re: Reverting to VS2013 on central and aurora

On Fri, May 6, 2016 at 12:39 PM, Benjamin Smedberg wrote: > I agree that we should drop support for non-SSE2. It mattered 7 years ago > (see https://bugzilla.mozilla.org/show_bug.cgi?id=500277) but it really > doesn't matter now. > > We do need to avoid updating these users to a build that will c

Re: Intent to deprecate: MacOS 10.6-10.8 support

On Fri, May 6, 2016 at 6:43 AM, Xidorn Quan wrote: > On Fri, May 6, 2016 at 8:24 PM, Mike Hommey wrote: > > > On Fri, May 06, 2016 at 06:01:12PM +1000, Xidorn Quan wrote: > > > > > > It's Firefox 48, three versions after ESR 45, which is roughly halfway > > > before the next ESR. > > > > 48 is t

Re: Updating 32-bit Windows users to 64-bit Windows builds?

Do we need this criteria? RAM - Does it hurt to move an instance that has <4GB? NPAPI - We've announced that we'll remove support this year [1]. Should we just wait until we do? Do we have a solution for Flash on Win64 that makes this viable? Lawrence [1] https://blog.mozilla.org/futurereleases/

Re: Intent to deprecate: MacOS 10.6-10.8 support

along, the tracking bug for the various pieces >> of >> client, updater, website, and SUMO changes are being tracked in bug >> 1255589. >> >> --BDS >> >> >> On Fri, May 13, 2016 at 2:15 PM, Nils Ohlmeier >> wrote: >> >> >>&g

Re: Tier-1 for Linux 64 Debug builds in TaskCluster on March 14 (and more!)

On Fri, May 20, 2016 at 11:27 AM, Nathan Froyd wrote: > On Fri, May 20, 2016 at 11:18 AM, Armen Zambrano G. > wrote: > > On 2016-05-19 08:29 PM, Mike Hommey wrote: > >> It's also not possible to *trigger* new TC jobs on treeherder ; like, > >> pushing with no try syntax and filling what you want

Two Factor Authentication and Github

You can ignore this email if you are not a member of the GitHub Mozilla organization. Starting on June 20th, the GitHub Mozilla organization will require Two Factor Authentication (2FA). We’re implementing 2FA for security reasons -- if you lose or have your password stolen, 2FA provides an extra

Re: Intent to deprecate: MacOS 10.6-10.8 support

On Tue, May 24, 2016 at 12:11 PM, Henrik Skupin wrote: > Mike Hommey wrote on 05/11/2016 05:06 AM: > >> The post states "Mozilla will end support for Firefox on OS X 10.6, > 10.7, > >> and 10.8 in August, 2016." This means that we will end support with the > >> Firefox 48 release. i.e. Firefox 48

Re: All about crashes

Hi Nick, Wasn't sure how you wanted feedback. Here's some in email form. "Crashes are caused by defects" Reading this I think it implies defects in Firefox. This is not always the case. Crashes are also the result of interactions with third party software. Both that that we designed for (like NP

Re: All about crashes

> > "Improve reproducibility of these crashes. > > > > Use rr to record crashes so they can be played back reliably." > > > > We're going to spin up a project to work on debugging in automation. > We've > > talked about having the ability to run a test until it fails and pause at > > that point. I

Re: Common crashes due to MOZ_CRASH and MOZ_RELEASE_ASSERT

We do have contacts. The more information we pass along about this crash including how to avoid crashing if we know the better our chances of success. What would you recommend that we tell IBM Rapport? Sylvestre - Can you please pass along information about the crash? Thanks, Lawrence On Tue, M

Re: 32-bit developer edition?

+ Javaun who should be able to fill in details about timing and what we want to do with Win64 and why On Fri, Jun 3, 2016 at 8:51 AM, Ben Kelly wrote: > On Jun 3, 2016 2:15 AM, "Jet Villegas" wrote: > > > > We should offer both. > > If we get a net reduction in OOMs with 64-bit it seems to me w

Re: Top crash list is odd right now

Is the plan to prompt on release as well? On Fri, Jun 3, 2016 at 11:33 AM, Andrew McCreight wrote: > blassey landed a patch to suggest that users submit unsubmitted crash > reports. This is going to make various kinds of crashes, like shutdown > crashes, grossly overrepresented in the crash-stat

MXR permanently offline, please transition to DXR

Mozilla Cross-Reference, better known as MXR (https://mxr.mozilla.org), was taken offline on June 13, 2016, to investigate a potential security issue. After careful review of the codebase, we have decided to accelerate the planned transition from MXR to its more modern equivalent, DXR ( https://dxr

Re: Faster gecko builds with IceCC on Mac and Linux

On Tue, Jul 5, 2016 at 6:58 PM, Ralph Giles wrote: > On Tue, Jul 5, 2016 at 3:36 PM, Gregory Szorc wrote: > > > * `mach build binaries` (touch network/dns/DNS.cpp): 14.1s > > 24s here. So faster link times and significantly faster clobber times. I'm > sold! > > Any motherboard recommendations? I

Re: MXR permanently offline, please transition to DXR

dev-platform was not included on my response below. Looping back in to this fork of the thread. On Fri, Jul 8, 2016 at 10:55 AM, Lawrence Mandel wrote: > Sorry Dao. I have seen some responses. Maybe they were off list. We're > working on details now. I'm going to get so

Re: MXR permanently offline, please transition to DXR

more > unobtrusive somehow? There are tons of mxr links all over the place, and > many of them are immutable. We don't gain anything by informing the viewer > about their obsolescence instead of showing them the content they want. > > On Fri, Jul 8, 2016 at 12:20 PM, Lawrence Mand

Re: MXR permanently offline, please transition to DXR

params from MXR links > and rewrites them to the equivalent DXR URL syntax: > https://addons.mozilla.org/en-US/firefox/addon/mxr-to-dxr-webextension/ . > > ~ Gijs > > > On 08/07/2016 20:27, Lawrence Mandel wrote: > > We do in the case of 3rd party software referencing files fr

Re: Checkin-needed requests - Please include complete information in the commit message :)

Autoland is not yet optimal but the team continues to work on it. Long term I think we want as much of our load to go through autoland as possible so that we can apply a consistent approach to how code is integrated into the tree. I would encourage you to use autoland. Tryserver wait times should b

Re: Proposed change to Commit Access Policy Level 3

+1 Good change. Lawrence On Wednesday, 3 August 2016, Mitchell Baker wrote: > Over time we've made a series of exceptions to the level 3 requirements > for Sheriffs and this proposal addresses that. > > > The current Policy for level 3 is: > > Level 3 - Core Product Access > >

Re: [Firefox Desktop] Issues found: October 3rd to October 7

Hi Amos, Thank you for sharing the issue that you're having with Firefox. We'll need a bug on file to flush out more details get traction on this. Have you filed a bug already? If not, can you please do so? https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=General Lawrence On

Re: Fwd: New Correlations on crash-stats

This is an amazing improvement to our ability to diagnose the cause of a crash. Excellent work Marco! Lawrence On Fri, Nov 4, 2016 at 4:58 AM, Sylvestre Ledru wrote: > As we say in French, rendering to Caesar that which isCaesar's: > > Marco = Marco Castelluccio > > Sylvestre > > > > Le 04/11/2

Re: Reduction of intermittent failures for Marionette tests

Thank you for your focus on intermittent Marionette tests Henrik. Great results! Lawrence On Wed, Nov 9, 2016 at 4:16 AM, Henrik Skupin wrote: > Hi all, > > Over the past months I tried to always have a look on newly filed > intermittent failures for Marionette tests on Bugzilla. I tried to > t

Increasing the platform meeting's relevance for engineers

tl;dr I would like to make the platform meeting more relevant for engineers. I have already made some changes (see below) and am interested in your feedback on what you would like to get out of this meeting. If you don't currently attend, what would make this meeting relevant for you? --- Sinc

Re: Increasing the platform meeting's relevance for engineers

of the active discussions and have the links to comment. We have not spent much time discussing any of these items in the meeting itself. Lawrence > > -Justin > > On Wed, Apr 24, 2013 at 2:26 PM, Lawrence Mandel > wrote: > > tl;dr > > I would like to make the platform mee

Re: Increasing the platform meeting's relevance for engineers

- Original Message - > I can definitely tell you what I liked and disliked about these > meetings, and why I stopped going to them. > > * Too many status updates. Putting the status updates in the wiki is > great. Reading over them when a lot of people are listening > synchronously is no

Re: Increasing the platform meeting's relevance for engineers

y of the > > people in attendance won't care about this particular issue, so > > we're > > just wasting their time. And similarly, at our current numeric and > > geographic scale it's inevitable that people who do care about the > > issue won't be in attendance

Re: Increasing the platform meeting's relevance for engineers

> Lawrence Mandel wrote: > > However, I have had people tell me that they do get some value from > > this meeting. > > > > What value did they get and what role did they have at mozilla? I am > wondering if the audience for this meeting is no longer mozilla &

Re: Increasing the platform meeting's relevance for engineers

- Original Message - > On Thu, Apr 25, 2013 at 8:02 AM, Lawrence Mandel < > lman...@mozilla.com > wrote: > > My understanding from speaking with a few people is that the > > platform > > meeting was once useful to engineers. > > Well, part of that p

Firefox/Gecko Development Meeting: Tue, Apr 30, 11am PT

The Firefox/Gecko development meeting is held weekly to discuss development team progress and issues related to the development of Firefox branded products and the Gecko platform. Actions from last week are here: https://wiki.mozilla.org/Platform/2013-04-30#Actions Meeting Details: * Agenda: h

Re: Storage in Gecko

- Original Message - > Great post, Taras! > > Per IRC conversations, we'd like to move subsequent discussion of > actions into a meeting so we can more quickly arrive at a resolution. > > Please meet in Gregory Szorc's Vidyo Room at 1400 PDT Tuesday, April > 30. > That's 2200 UTC. Apolo

Re: [Advance warning] Session Restore is changing, will break add-ons

cc Jorge Villalobos. - Original Message - > As part of project Async, we have been working on refactoring > Firefox’ > Session Restore to ensure that it does not block the main thread. > Part > of the work has been cleaning up the code and the data structures > involved in Session Restore

What should be next for the platform meeting?

After my previous post about the platform meeting, I received some good feedback. The general feeling about the platform meeting seems to be: 1. it has some useful content/purpose that we want to maintain 2. it has no particular focus and is not optimized for anyone For 1, the uses that I've hea

Platform meeting changes effective June 2013

tl;dr The platform meeting will revert to focus on engineering teams as of next week. We discussed the platform meeting's use during today's platform meeting. The consensus of the people who attended the meeting is that the platform meeting is useful and should be continued. Here is my summary

Re: Platform meeting changes effective June 2013

of hours in advance of the meeting. Would that be enough time to let you decide if you want to attend? Lawrence > > Cheers, > Ehsan > > On 2013-05-28 5:10 PM, Lawrence Mandel wrote: > > tl;dr The platform meeting will revert to focus on engineering > > teams as of nex

Re: Platform meeting changes effective June 2013

- Original Message - > On 30/05/13 04:55, Mike Hommey wrote: > > As someone that will soon be in UTC+9, and taking on the occasion > > to > > represent all the people in that timezone and surroundings, a > > couple > > hours before 3am is not very a great time to decide whether I'd > > atte

Re: Embracing git usage for Firefox/Gecko development?

- Original Message - > On Fri, May 31, 2013 at 2:56 AM, Johnny Stenback > wrote: > > Option 2 is where this discussion started (in the Tuesday meeting a > > few > > weeks ago, > > https://wiki.mozilla.org/Platform/2013-05-07#Should_we_switch_from_hg_to_git.3F). > > Since then I've had a

Engineering/Platform meeting reboot summary

As I previously posted, this week we rebooted the Engineering/Platform meeting. I blogged about the changes. http://lawrencemandel.com/2013/06/06/mozilla-engineeringplatform-meeting-reboot/ Lawrence ___ dev-platform mailing list dev-platform@lists.mozi

Update: Engineering meeting locations

I'll keep this short. There are changes to the meeting locations for the Engineering/Platform (Tue, 11am PT) meeting. SFO: Warfield (change to provide more space) TOR: Finch (change to avoid conflict with TOR Commons) MTV: Warp Core (no change) Remote: Engineering Vidyo room (no change) Lawrence

Engineering meeting to be broadcast on Air Mozilla starting Aug 6, 2013

The weekly Engineering meeting will be broadcast on Air Mozilla starting this coming week (Aug 6, 2013). The reasons for broadcasting this meeting on Air Mozilla are to: 1. provide a recording of the meeting for those who unable to attend at the scheduled time 2. make it easier for people to at

Engineering Meeting: Tue, Aug 13, 11am PT

The Engineering meeting is a weekly time to discuss the work of engineering teams and share information relevant to the day-to-day work of engineers. Meeting Details: * Agenda: https://wiki.mozilla.org/Platform/2013-08-13 * Engineering Vidyo Room and Air Mozilla * https://v.mozilla.com/flex.html

Re: Summit Innovation Fair: Improving developer productivity at Mozilla?

- Original Message - > At the summit's Innovation Fairs, Mozilla's program management team will > be hosting "Developer Productivity" booths to gather suggestions for > streamlining our development processes and reducing developer frustration. > > What speed bumps are getting you down? Har

Re: Feature tracking via bug keyword

- Original Message - > Lukas Blakk wrote: > > This wiki page: https://wiki.mozilla.org/Features/Release_Tracking > > now picks up on the keyword 'feature' in your meta/tracking bugs. > > > > Please add this to your feature work to make sure it gets early QA, > > Stability, PR, User Advocacy

Re: Feature tracking via bug keyword

- Original Message - > On 16/10/2013 22.02, Lukas Blakk wrote: > > This wiki page: https://wiki.mozilla.org/Features/Release_Tracking now > > picks up on the keyword 'feature' in your meta/tracking bugs. > > I've set the keyword and milestone on bug 907082 but don't see it in: > > https:/

Re: Mozilla development "bootcamp"

cc Lukas and Mark, who have started looking at onboarding material for new corporate partners. We also discussed a similar topic in our Oct monthly epm meetup (last week). Lukas has initiated a conversation with Amie to see about incorporating similar material into the employee onboarding expe

Re: Mozilla development "bootcamp"

- Original Message - > Added to the etherpad too but here's the list I have so far. > > I started a github project a month or so ago here: (Still pretty early) > https://github.com/bbondy/codefirefox/ > > And here are some videos, layout will be changing, that's just temporary: > http://c

Re: A/B testing with telemetry

- Original Message - > Do we have a formalized way to do A/B testing with telemetry? That is, > assuming that there is a telemetry probe that measures problem > symptoms and a boolean pref for turning on a potential solution, is > there a way the declare the pref as something that telemetr

Re: On closing old bugs

- Original Message - > On 27/11/13 07:36, Gabriele Svelto wrote: > > I'm always tempted to close the former as duplicates of the actual fix > > and the latter as WONTFIX so that they won't show up on the following > > searches but I'm also afraid that closing a bug several years old is > >

Re: Exposing (mobile) device info via the user agent or HTTP headers

- Original Message - > On Friday, April 1, 2011 11:38:27 AM UTC-4, Benjamin Smedberg wrote: > > Discussion followup to bug 625238 > > . > > Hi, > > After reading through this discussion thread as well as the comments on the > bug report

Re: FYI: Nightly 28 uplift in 7 days

- Original Message - > This is a friendly reminder that the next channel merge date [1] is only > 7 days away! So don't forget to land those last minute bug fixes this > week. :) Also, you may want to hold destablizing or less important > changes until next week for Nightly 29. As Gavin me

Re: On closing old bugs

- Original Message - > Lawrence Mandel writes: > > > - Original Message - > >> On 27/11/13 07:36, Gabriele Svelto wrote: > >> > I'm always tempted to close the former as duplicates of the > >> > actual fix and the latter a

Re: On closing old bugs

years. Lawrence > -- > - Milan > > On 2013-12-04, at 14:15 , Lawrence Mandel wrote: > > > - Original Message - > >> Lawrence Mandel writes: > >> > >>> - Original Message - > >>>> On 27/11/13 07:36, Gabriele Svelto wrote:

Re: On closing old bugs

- Original Message - > On Tuesday 2013-12-03 21:15 -0800, Lawrence Mandel wrote: > > I'm taking a stronger stance and suggesting that we should be able to > > wontfix bugs that likely aren't worth anyone's time or attention. As a > > concrete examp

Re: On closing old bugs

- Original Message - > On Tue, Dec 3, 2013 at 9:15 PM, Lawrence Mandel wrote: > > > > I would assert that if a bug hasn't been fixed in 10 years it probably > > isn't important enough to spend time on now. > > I strongly disagree with this statement,

Re: On closing old bugs

- Original Message - > On 12/3/2013 11:15 PM, Lawrence Mandel wrote: > > In fact, there at 6925 bugs across all Bugzilla products currently in > > the new or unconfirmed state that were opened more than 10 years ago. > > I would assert that if a bug hasn't

Re: On closing old bugs

- Original Message - > On 12/4/2013 2:30 PM, Lawrence Mandel wrote: > > I think David, Nick, Henri, and you are right - there are lots of old bugs > > that we each think are important enough to fix. (Yes, I have some as > > well.) In my mind the real question is, given

Re: Intent to deploy: plugin timeout A/B test experiment, bug 1018200

I missed this earlier. Lacking any major concerns (Jet did express one), I approve the deployment of this experiment on Beta 32 on behalf of release management. Lawrence - Original Message - > This is an official notice of intent to deploy the experiment in bug > 1018200 to the beta cha

CHANGE: Next merge date is Tue, Sep 2, 2014

(Cross posting for visibility. Followups to dev-planning please.) The next merge was scheduled for Mon, Sep 1, 2014, which is labour day in Canada and the US. In order to accommodate holiday schedules, the merge will instead occur on Tue, Sep 2, 2014. This change will have no impact on the Fire

Firefox 34 release date moving to Dec 1/2

The Firefox 34 release date will move out one week from Nov 25 to Dec 1/2. This change impacts Firefox Desktop, Firefox for Android, Firefox ESR, and Thunderbird. The purpose of this change is to allow for an additional week of stabilization during the 34 cycle. Details of the change: - Release

Re: Updating the policy for Talos performance regression in 2015

Old thread but now that we're 3 months into 2015, has this new policy been effective at getting perf regressions fixed or at least deliberately accepted? Lawrence On Fri, Dec 19, 2014 at 1:33 PM, wrote: > Great questions folks. > > :bsmedberg has answered the questions quite well, let me elabor

Re: changing the default platform and operating-system on bugzilla.mozilla.org to all / all

+1 to Milan's suggestion. These fields are used somewhat consistently on stability and graphics bugs, which release management pays attention to. If we are going to continue with the fields, I like the idea of "Not specified" as that makes it clear that no value was set whereas "All" is currently u

Snappy Meeting, Thurs. July 26, 11am PT

Colin Greenwood said [1], "The guitar is a much more efficient machine than a computer. More responsive." Discuss. And, join us this Thursday, 11am PT, to discuss Firefox responsiveness. Please add your items and status to the agenda before the call. https://etherpad.mozilla.org/snappy Dial-in:

Update your Snappy status Aug 2 (no meeting this week)

Happy Snappy off week. Please update your status and any open issues to the etherpad by EOD Thursday, Aug. 2, 2012. https://etherpad.mozilla.org/snappy Lawrence ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/list

Re: "Touch" or "Tablet"?

> http://blogs.msdn.com/b/ie/archive/2012/07/12/ie10-user-agent-string-update.aspx > > IE10 has introduced the Touch token to the UA string, which overlaps > in > intent with our Tablet token. > > Dao suggests it would be nice to get cross-browser consistency here. > https://bugzilla.mozilla.org/

Snappy Meeting, Thurs. Aug 9, 11am PT

Join us this Thursday, 11am PT, to discuss Firefox responsiveness. Please add your items and status to the agenda before the call. https://etherpad.mozilla.org/snappy (I was late archiving last week's status. Apologies if I blew away anyone's update for this week. You can recover it at https://

Preliminary results of aliasing Webkit CSS properties in Gecko analysis

The Layout, QA, and Market Insight teams recently analyzed the impact of aliasing Webkit CSS properties in Gecko with the goal of answering the question, Does aliasing a subset of Webkit CSS properties in Gecko improve mobile Web compatibility? The results thus far indicate that there is a very

Update your Snappy status Aug 16 (no meeting this week)

Were you Snappy this week? Tell the world. Please update your status and any open issues to the etherpad by EOD Thursday, Aug. 16, 2012. https://etherpad.mozilla.org/snappy Lawrence ___ dev-platform mailing list dev-platform@lists.mozilla.org https://l

Re: Preliminary results of aliasing Webkit CSS properties in Gecko analysis

Cross posting to dev-planning to ensure that the planning audience sees these preliminary results. Please post and responses to dev-platform. - Original Message - > The Layout, QA, and Market Insight teams recently analyzed the impact > of aliasing Webkit CSS properties in Gecko with the

Snappy Meeting, Thurs. Aug 23, 11am PT

We're not the bear we're the fox! http://www.cartoonstock.com/directory/r/responsive_to_needs_gifts.asp Join us this Thursday, 11am PT, to discuss Firefox responsiveness. Please add your items and status to the agenda before the call. https://etherpad.mozilla.org/snappy Dial-in: conference# 9534

Update your Snappy status Aug 30 (no meeting this week)

Fair warning, this is a solicitation request. I want your Snappy news! Now! Just any news just won't do. Gimme, gimme Snappy news from the past week. You amazing individuals who contribute Snappy news to the wondrous and sometimes awe inspiring Snappy etherpad will be rewarded handsomely with

Snappy Meeting, Thurs. Sep 6, 11am PT

This Thursday, 11am PT, will be our last Snappy meeting before our work week. Please add your items and status to the agenda before the call. https://etherpad.mozilla.org/snappy Dial-in: conference# 95346 US/International: +1 650 903 0800 x92 Conf# 95346 US toll free: +1 800 707 2533 (pin 369) C

Re: Adding hardware tokens to UA string

> > Hi All, > > > > For Firefox OS, we are getting requests from partners to add tokens > > to > > the UA string which identify the hardware device on which Firefox > > OS > > is running. > > > > During the UA discussions for Firefox for Android we explicitly > decided not > to do this (after much

Re: Adding hardware tokens to UA string

> > Let me know what you think. > > Since Firefox OS is openly accessible to hardware vendors, wouldn't > it > be easy for them to override any decision made by Mozilla if they or > their content partners would prefer it that way? We have the ability to set the terms for use of the Firefox brand.

Snappy Meeting, Thurs. Sep 20, 11am PT

After our Snappy work week I'm left feeling energized yet sluggish. (MozFlu will do that to you.) I look forward to hearing your Snappy updates this Thursday at 11am PT. Please add your items and status to the agenda before the call. https://etherpad.mozilla.org/snappy Dial-in: conference# 9534

  1   2   >