Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
mozilla.dev.planning
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion Trunk Sheriffs
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Justin Dolske  
View profile  
 More options May 22 2007, 12:31 am
Newsgroups: mozilla.dev.planning
From: Justin Dolske <dol...@mozilla.com>
Date: Mon, 21 May 2007 21:31:39 -0700
Local: Tues, May 22 2007 12:31 am
Subject: Re: Trunk Sheriffs
Print | View thread | Show original | Report this message | Find messages by this author

Boris Zbarsky wrote:
> It all depends on your task set and on your environment.

> For example, on my machine (Linux)

"Oh, Linux."

You've got a point there. At least, my impression is that Linux needs
the most help of the 3 main platforms.

Were you just using SVG on Linux as an example to hilight differences in
task set / environment, or have there been recent regressions (Cairo :-)
  that started killing X?

> Some of both; net benefit is hard to gauge because the cost-benefit
> equation is so different for different people and in different situations.

Absolutely.

>> My general impression is that while there are
>> certainly a number of annoyances and quirks, it's entirely
>> dogfoodable.

> Your text inputs must work more often than mine do, then.

Probably not! I end up doing the same kinds of workarounds as you
mention, but I just haven't personally found it to be something that
stops me from getting work done. I suppose this is the kind of
regression that falls into the "death by a thousand papercuts" category...

> I feel that we need to:

> 1)  Nominate bugs for blocking Gecko 1.9 (or Firefox 3) as needed
> 2)  Triage said nominations, with regressions likely getting
>     blocking status
> 3)  Find people to fix the blocking bugs.

Perhaps we should track 'dogfood' bugs as a standard part of the weekly
FF3/Gecko meetings? Although, being more aggressive about backing out
new regressions is probably (but not always) a more efficient way to do
that for the future.

I also wonder if it might help to have longer terms for sheriffs? Say, 2
days to a week? That might help by having stronger ownership for backing
out checkins which don't immediately manifest themselves as a flaming
tinderbox inferno.

Justin


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google