James Graham wrote on 2018-11-28 13:20:
On 28/11/2018 20:15, Mark Côté wrote:
My team has pretty much nothing to do with the gecko GitHub clone; we
need to keep our focus on the "standard" workflow.
Sure, the problem is that it's an attractive nuisance for new
contributors who find it and go
On 11/28/2018 01:20 PM, James Graham wrote:
On 28/11/2018 20:15, Mark Côté wrote: * It's not obvious to people
that patches can't go up for review
without
a preexisting bug, and won't actually be reviewed unless they
specify a
reviewer in the commit message (or go into
On Wed, Nov 28, 2018 at 09:20:17PM +, James Graham wrote:
> On 28/11/2018 20:15, Mark Côté wrote:
> > We're still working through a longer-term vision that we'll share early
> > next year, but I can answer some questions now.
>
> Thanks, this is helpful!
>
> > * Have to make a choice
On 28/11/2018 20:15, Mark Côté wrote:
We're still working through a longer-term vision that we'll share early
next year, but I can answer some questions now.
Thanks, this is helpful!
* Have to make a choice early on about whether to learn a relatively
unfamiliar (to the majority of
On Wed, Nov 28, 2018 at 1:34 PM James Graham wrote:
> Can you share with us the long term vision for what the workflow is
> going to look like here? I've recently seen a few cases where
> experienced develoeprs who have either never contributed to gecko before
> or contribute infrequently tried
On 27/11/2018 17:46, Kim Moir wrote:
Speeding up moz-phab
moz-phab[2] is Engineering Workflow’s officially supported custom
command-line interface to Phabricator, built in order to better support the
“stacked commits” workflow that is common in Firefox engineering.
Unfortunately some of the
For a richer version of this newsletter, please see <
https://docs.google.com/document/d/1uJECrrYitWbuyLJl_W_QHaBJtYcabJsAv2aQdFSmr3E/
>.
Hello from the Engineering Workflow team! This is our first newsletter.
Exciting! But first, who are we and what do we do? The Engineering Workflow
team[1]
7 matches
Mail list logo
