Re: Graceful Platform Degradation

2014-03-27 Thread Cameron Kaiser
For different browsers running on the same machine, some given content might perform poorly or well, depending on how features are implemented. In (1) we might want to reduce quality/correctness to make the experience better for the user. If the user finds that content doesn’t work performantly i

Re: Spring cleaning: Reducing Number & Footprint of HG Repos

2014-03-27 Thread Joshua Cranmer 🐧
On 3/27/2014 12:11 PM, Andrew Sutherland wrote: On 03/27/2014 10:10 AM, Joshua Cranmer 🐧 wrote: It's worth noting that hg-git is having some performance issues with github right now. A basic clone of a 1MB repository takes well over a minute before it starts doing anything. When I was convert

Re: Spring cleaning: Reducing Number & Footprint of HG Repos

2014-03-27 Thread Andrew Sutherland
On 03/27/2014 10:10 AM, Joshua Cranmer 🐧 wrote: It's worth noting that hg-git is having some performance issues with github right now. A basic clone of a 1MB repository takes well over a minute before it starts doing anything. When I was converting my repositories last night I found that altho

Re: Spring cleaning: Reducing Number & Footprint of HG Repos

2014-03-27 Thread Randell Jesup
>*User Repos* >TLDR: I would like to make user repos read-only by April 30th. We should >archive them by May 31st. As mentioned, too fast. >Time spent operating user repositories could be spent reducing our >end-to-end continuous integration cycles. If we're spending any significant time or mo

Re: Spring cleaning: Reducing Number & Footprint of HG Repos

2014-03-27 Thread Gregory Szorc
On 3/27/14, 6:37 AM, Justin Wood (Callek) wrote: On 3/26/2014 9:15 PM, Taras Glek wrote: Bobby Holley Wednesday, March 26, 2014 17:27 I don't understand what the overhead is. We don't run CI on user repos. It's effectively just ssh:// + disk space, right? That s

Re: Spring cleaning: Reducing Number & Footprint of HG Repos

2014-03-27 Thread Robert Kaiser
Taras Glek schrieb: *User Repos* TLDR: I would like to make user repos read-only by April 30th. When that happens, I will stop running any custom crash reports and dashboards that the stability program depends on, at least until further notice. I do not want to run a non-Mozilla-hosted repo f

Re: Spring cleaning: Reducing Number & Footprint of HG Repos

2014-03-27 Thread David Burns
What are "mission critical" repos since you just put everything in the same list? If we start removing project branches to be put on outsourced VCS we remove any sheriff support for that project branch since, as been pointed out many times, we dont have access to the server side commit hook

Re: Spring cleaning: Reducing Number & Footprint of HG Repos

2014-03-27 Thread James Graham
On 27/03/14 14:17, Armen Zambrano G. wrote: On 14-03-26 08:27 PM, Bobby Holley wrote: I don't understand what the overhead is. We don't run CI on user repos. It's effectively just ssh:// + disk space, right? That seems totally negligible. FTR from an operations standpoint, it is never "just".

Re: Spring cleaning: Reducing Number & Footprint of HG Repos

2014-03-27 Thread Gijs Kruitbosch
On 27/03/2014 13:43, Justin Wood (Callek) wrote: On 3/27/2014 2:58 AM, Doug Turner wrote: Want to move to github? (0) sudo apt-get install python-setuptools (1) sudo easy_install hg-git (2) add |hggit =| under [extensions] in your .hgrc file (3) Go to GitHub.com and create your new repo. (4) cd

Re: Spring cleaning: Reducing Number & Footprint of HG Repos

2014-03-27 Thread Armen Zambrano G.
On 14-03-26 08:27 PM, Bobby Holley wrote: > I don't understand what the overhead is. We don't run CI on user repos. > It's effectively just ssh:// + disk space, right? That seems totally > negligible. > FTR from an operations standpoint, it is never "just". Never. If it was *just* we wouldn't even

Re: Spring cleaning: Reducing Number & Footprint of HG Repos

2014-03-27 Thread Joshua Cranmer 🐧
On 3/27/2014 1:58 AM, Doug Turner wrote: Want to move to github? (0) sudo apt-get install python-setuptools (1) sudo easy_install hg-git (2) add |hggit =| under [extensions] in your .hgrc file (3) Go to GitHub.com and create your new repo. (4) cd (5) hg bookmark -r default master (6) hg push gi

Re: Spring cleaning: Reducing Number & Footprint of HG Repos

2014-03-27 Thread Justin Wood (Callek)
On 3/27/2014 2:58 AM, Doug Turner wrote: Want to move to github? (0) sudo apt-get install python-setuptools (1) sudo easy_install hg-git (2) add |hggit =| under [extensions] in your .hgrc file (3) Go to GitHub.com and create your new repo. (4) cd (5) hg bookmark -r default master (6) hg push gi

Re: Spring cleaning: Reducing Number & Footprint of HG Repos

2014-03-27 Thread Axel Hecht
On 3/27/14, 12:53 AM, Taras Glek wrote: *User Repos* TLDR: I would like to make user repos read-only by April 30th. We should archive them by May 31st. Time spent operating user repositories could be spent reducing our end-to-end continuous integration cycles. These do not seem like mission-cr

Re: Spring cleaning: Reducing Number & Footprint of HG Repos

2014-03-27 Thread Justin Wood (Callek)
On 3/27/2014 1:11 AM, Mike Hommey wrote: On Wed, Mar 26, 2014 at 05:40:36PM -0700, Gregory Szorc wrote: On 3/26/14, 4:53 PM, Taras Glek wrote: *User Repos* TLDR: I would like to make user repos read-only by April 30th. We should archive them by May 31st. Time spent operating user repositories

Re: Spring cleaning: Reducing Number & Footprint of HG Repos

2014-03-27 Thread Justin Wood (Callek)
On 3/26/2014 9:15 PM, Taras Glek wrote: Bobby Holley Wednesday, March 26, 2014 17:27 I don't understand what the overhead is. We don't run CI on user repos. It's effectively just ssh:// + disk space, right? That seems totally negligible. Human overhead in keepin

Re: Spring cleaning: Reducing Number & Footprint of HG Repos

2014-03-27 Thread Armen Zambrano G.
On 14-03-26 07:53 PM, Taras Glek wrote: > *User Repos* > TLDR: I would like to make user repos read-only by April 30th. We should > archive them by May 31st. > > Time spent operating user repositories could be spent reducing our > end-to-end continuous integration cycles. These do not seem like

Re: Spring cleaning: Reducing Number & Footprint of HG Repos

2014-03-27 Thread jmaher
For talos development we allow pointing at a user specific repo instead of the master one. This has greatly reduced the time to bring up new tests. This could easily be hosted elsewhere, but we chose to restrict it to user repos for a security measure. You have to have cleared some form of ba

Re: Graceful Platform Degradation

2014-03-27 Thread Nicholas Nethercote
This sounds like a worthy and interesting idea, but also a very difficult one. > PC games allow the user to turn certain features (mostly graphics > related ones) on and off so that they can find their own level of > acceptable performance/quality. This doesn't seem like the right > approach for

Re: Spring cleaning: Reducing Number & Footprint of HG Repos

2014-03-27 Thread Doug Turner
Most of mine were patch queues. Your results may vary. On Thursday, March 27, 2014, Mike Hommey wrote: > On Wed, Mar 26, 2014 at 11:58:48PM -0700, Doug Turner wrote: > > Want to move to github? > > > > (0) sudo apt-get install python-setuptools > > (1) sudo easy_install hg-git > > (2) add |hgg

Re: Spring cleaning: Reducing Number & Footprint of HG Repos

2014-03-27 Thread Mike Hommey
On Wed, Mar 26, 2014 at 11:58:48PM -0700, Doug Turner wrote: > Want to move to github? > > (0) sudo apt-get install python-setuptools > (1) sudo easy_install hg-git > (2) add |hggit =| under [extensions] in your .hgrc file > (3) Go to GitHub.com and create your new repo. > (4) cd > (5) hg bookmar