(please direct followups to dev-planning, cross-posting to governance,
firefox-dev, dev-platform)
Nearly 19 years after the creation of the Mozilla Project, commit access
remains essentially the same as it has always been. We've evolved the
vouching process a number of times, CVS has long since
I think the rule is fine, subject to the reality that the scope of totally
new doc-level UX is fairly limited. I think you'll want to be a little
more aggressive up front if you want to shift the overall codebase in
finite time.
To that end, I'd propose an additional requirement that any major re
If this is a serious problem, and I can easily believe that it is, have we
considered having a default behaviour of cancelling all unfinished Try jobs
running for a given user when they push again? Based on how I've seen
people use Try over the years, I suspect a significant majority of pushes
are
On Sat, Jan 23, 2016 at 11:11 AM, Eric Rescorla wrote:
> Following up in this. We're not the first people to have autoland, so is
> there some reason
> not to simply copy what others do here. Specifically, here's the Chromium
> commitbot
> behavior: https://www.chromium.org/developers/testing/com
ew do most of the experimentation with the workflow.
I've changed a ton of stuff in Bugzilla over the years, which is why I
tacked on the low risk alternative. :)
On Fri, Jan 22, 2016 at 2:12 AM, Gregory Szorc wrote:
> On Thu, Jan 21, 2016 at 10:37 PM, Mike Connor wrote:
>
>> Li
Like Greg, I'm a big fan of reviewer-lands-if-ready. It's a huge
simplification of workflow, saves developers time, and lets machines do
work instead of humans. That said, I don't think we should be surprising
people or unilaterally imposing changes to their workflow. The best way to
do this is to
On 5 July 2015 at 11:53, Dirkjan Ochtman wrote:
> On Sun, Jul 5, 2015 at 5:11 PM, Anne van Kesteren
> wrote:
> > Is there a reason we shouldn't expose a hook for this?
>
> On the one hand, this seems really useful. On the other hand, I'm
> pretty worried about the UX implications here. I wouldn'
> On Dec 12, 2014, at 6:21 PM, Ehsan Akhgari wrote:
>
> On 2014-12-12 6:16 PM, Jonas Sicking wrote:
>> On Fri, Dec 12, 2014 at 3:12 PM, Martin Thomson wrote:
>>> Why not simply provide a way to show the password always? I believe that
>>> Microsoft always provides the little eye icon in their
8 matches
Mail list logo
