lets all try
I'm
> On 14 Jul 2017, at 13:48, Jim Blandy wrote:
>
> 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 a
On 7/14/17 1:31 AM, Jim Blandy wrote:
But keeping all the comments in one thread is a mixed blessing, too
Absolutely.
I guess what I'm saying is we should try to have some guidelines for
when it's appropriate to take the discussion back to the bug instead of
continuing it in the review...
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 top of the thread he
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 wil
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 don'
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 bad for patches to be duplicated into b
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 phabricator for code review
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 normal
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 https://bugzilla.mozilla.org/show_bug.
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 fro
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 woul
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 di
>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
>> phabricate reviews
>>> 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 migrated
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
[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 Firefo
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 compl
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 Thursday
18 matches
Mail list logo
