[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cross-project-issues-dev] yesterday's server outages
- From: Ralf Sternberg <rsternberg@xxxxxxxxxxxxxxxxx>
- Date: Thu, 16 Feb 2012 14:13:31 +0100
- Delivered-to: email@example.com
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eclipsesource.com; s=eclipsesource; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=CuyrT9nUPPpbSEN66y7sJQ93mKnstqSI68hMQBOm+Ig=; b=PtALnI0ZK9mWkzbvlpSokNbf4TpjGevZMNraWfYlHNJz24ur5kRYokTEPNPmAm192x YxZjHFxiyNNmxOTCOz3cLQd9KoYXIe1jT7Ezn0Qx3+IMvUKzkaKm1et57N0hpAgnRCd4 C4wQQEbXbTwjuLHv5fGeBLltBgxiMDq1sVcIo=
I agree that it would be helpful to be informed of such infrastructure
problems earlier. When you know that there are problems and they're
going to be fixed, you can just rearrange your work items instead of
searching for the cause of problems. Yesterday, I found out somewhere
on Twitter that others are having problems too. The mail on
committer's list came when the issue was already fixed.
I understand that the committer mailing list does not work in case of
a total outage, maybe a dedicated twitter account would make sense?
On Thu, Feb 16, 2012 at 12:53, Denis Roy <denis.roy@xxxxxxxxxxx> wrote:
> On 02/16/2012 05:47 AM, Markus Knauer wrote:
>> Up to now I don't really know what happened (I've seen some random
>> snippets of information on Twitter, here a bug from some committers, there a
>> message on the mailing list from other committers), but what I do know is
>> that a lot of us committers wasted time on tracking down problems in *their*
>> projects, problems that were in fact related to infrastructure problems.
> Markus, ÂI posted up on the committers mailing list, since this was a total
> outage, and that list reaches many more people.
> I'll post another update as soon as I have more information.
> cross-project-issues-dev mailing list