Re: Phabricator Update, July 2017

2017-07-13 Thread Jim Blandy
Yeah, this is kind of the opposite of "No New Rationale". https://air.mozilla.org/friday-plenary-rust-and-the-community/ On Thu, Jul 13, 2017 at 2:49 PM, David Anderson wrote: > On Thursday, July 13, 2017 at 1:38:18 PM UTC-7, Joe Hildebrand wrote: > > I'm responding at the

Re: Phabricator Update, July 2017

2017-07-13 Thread Jim Blandy
Many people seem to be asking, essentially: What will happen to old bugs? I'm trying to follow the discussion, and I'm not clear on this myself. For example, "Splinter will be turned off." For commenting and reviewing, okay, understood. What about viewing patches on old bugs? Yes, Phabricator

Re: Phabricator Update, July 2017

2017-07-13 Thread Boris Zbarsky
On 7/13/17 9:04 PM, Mark Côté wrote: It is also what newer systems do today (e.g. GitHub and the full Phabricator suite) I should note that with GitHub what this means is that you get discussion on the PR that should have gone in the issue, with the result that people following the issue

Re: Phabricator Update, July 2017

2017-07-13 Thread Gregory Szorc
On Thu, Jul 13, 2017 at 6:04 PM, Mark Côté wrote: > On 2017-07-13 3:54 PM, Randell Jesup wrote: > >> On Wed, Jul 12, 2017 at 11:27 AM, Byron Jones wrote: >>> >>> But indeed having also the patches in bugzilla would be good. > > no, it would be

Re: Phabricator Update, July 2017

2017-07-13 Thread Mark Côté
On 2017-07-13 3:54 PM, Randell Jesup wrote: On Wed, Jul 12, 2017 at 11:27 AM, Byron Jones wrote: But indeed having also the patches in bugzilla would be good. no, it would be bad for patches to be duplicated into bugzilla. we're moving from bugzilla/mozreview to

Merge Day changes coming up soon

2017-07-13 Thread Liz Henry (:lizzard)
Hi there, Release management and release engineering have changed the dates for the next release cycle's merge day. Firefox 56 will move to mozilla-beta, and Firefox 57 will become Nightly, on August 2 (rather than August 7). You should still be able to check in patches to mozilla-central

Re: More Rust code

2017-07-13 Thread Nicholas Nethercote
On Tue, Jul 11, 2017 at 11:03 AM, Nicholas Nethercote < n.netherc...@gmail.com> wrote: > > >> The first thing comes to my mind is crash reports. It currently doesn't >> always include useful panic message from Rust, see for example [1] and [2]. >> > > I filed

Re: Phabricator Update, July 2017

2017-07-13 Thread David Anderson
On Thursday, July 13, 2017 at 1:38:18 PM UTC-7, Joe Hildebrand wrote: > I'm responding at the top of the thread here so that I'm not singling out any > particular response. > > We didn't make clear in this process how much work Mark and his team did > ahead of the decision to gather feedback

Re: More Rust code

2017-07-13 Thread Mike Hommey
On Wed, Jul 12, 2017 at 04:06:39PM -0700, Eric Rahm wrote: > Interesting points. > >- *using breakpad* - was the problem that creating wrappers to access >the c/c++ code was too tedious? Could bindgen help with that, if not it >would be interesting gather some details about why it

Re: Phabricator Update, July 2017

2017-07-13 Thread Joe Hildebrand
I'm responding at the top of the thread here so that I'm not singling out any particular response. We didn't make clear in this process how much work Mark and his team did ahead of the decision to gather feedback from senior engineers on both Selena and my teams, and how deeply committed the

Re: Phabricator Update, July 2017

2017-07-13 Thread Randell Jesup
>On Wed, Jul 12, 2017 at 11:27 AM, Byron Jones wrote: > >> But indeed having also the patches in bugzilla would be good. >>> >> no, it would be bad for patches to be duplicated into bugzilla. we're >> moving from bugzilla/mozreview to phabricator for code review, duplicating >>

Re: Phabricator Update, July 2017

2017-07-13 Thread Randell Jesup
>>> To answer the other part of your question, MozReview will be disabled for >>> active use across the board, but it is currently used by a small number of >>> projects. Splinter will be disabled on a per-product basis, as there may be >>> some projects that can't, won't, or shouldn't be

mozilla-central is closed for lack of mac symbols/crash data

2017-07-13 Thread Benjamin Smedberg
Starting with Monday's nightly we've discovered that we're missing mac symbols for the XUL library. Because this makes crash statistics useless, this means that we can't bisect or detect most crash issues on mac. For that reason, I've asked sheriffs to close the tree. This is being tracked in bug

Re: More Rust code

2017-07-13 Thread Selena Deckelmann
[moving dev-platform and firefox-dev to Bcc] What I've heard in this thread is that we have a few blockers, some pain points and bugs to file regarding more Rust integration with Firefox. Nick -- please ensure those bugs get filed, and a meta-bug entitled "Make the developer experience for

Re: More Rust code

2017-07-13 Thread Enrico Weigelt, metux IT consult
On 10.07.2017 12:29, Nicholas Nethercote wrote: Hi folks, Firefox now has multiple Rust components, and it's on track to get a bunch more. See https://wiki.mozilla.org/Oxidation for details. I wonder which of the pressing problems (eg. massing resource wasting, bad performance, horribly

Proposed W3C Charter: (Accessibility) Education and Outreach Working Group

2017-07-13 Thread L. David Baron
The W3C is proposing a revised charter for: (Accessibility) Education and Outreach Working Group https://www.w3.org/WAI/EO/charter2017 https://lists.w3.org/Archives/Public/public-new-work/2017Jul/0003.html Mozilla has the opportunity to send support, comments, or objections through