Le 21/03/2014 21:15, Adam Conrad a écrit :
This happens anyway, as people other than you are developing around
you. You don't have control over the entire archive (and won't ever
have it), so even if the snapshot in time that you tested at 17:40
yesterday was just how you wanted it, something wi
On Fri, Mar 21, 2014 at 01:56:26PM -0400, Michael Terry wrote:
>
> For example, my feature depends on fixes in Ted's indicator silo and Boiko's
> telephony silo. So as delayed as they are, I'm even further down the list.
I've said this before, and I'll say it again. You can't do massively
integ
On Fri, Mar 21, 2014 at 09:11:37PM +0100, Sebastien Bacher wrote:
>
> The issue with that is that when you let a portion migrates by
> itself, then nobody has tested that set in an isolated way. It could
> be that the changes you let in required another piece from the
> proposed set that you didn'
Le 21/03/2014 21:03, Adam Conrad a écrit :
If all these features landed in -proposed, they could be tested and
integrated together, a blocking bug could keep some bits from migrating
early, if that was warranted, but the key is that it would all be there
together, to see if it all integrates toge
On Fri, Mar 21, 2014 at 10:08 AM, Alexander Sack wrote:
> On the front of data, we haven't seen much new. For instance we only
> know about a single case where this "all halt" event has negative
> impact; so please speak up if you are affected.
>
I'm trying to shepherd through the big split gree
On 21 March 2014 14:08, Alexander Sack wrote:
>
> On the front of data, we haven't seen much new. For instance we only
> know about a single case where this "all halt" event has negative
> impact; so please speak up if you are affected.
>
Similar to Colin, I am deeply and negatively impacted by "
On Fri, Mar 21, 2014 at 11:08 AM, Alexander Sack wrote:
>
> On the front of data, we haven't seen much new. For instance we only
> know about a single case where this "all halt" event has negative
> impact; so please speak up if you are affected.
>
There are at least two big telephony features p
On Fri, Mar 21, 2014 at 03:08:19PM +0100, Alexander Sack wrote:
> On the front of data, we haven't seen much new. For instance we only
> know about a single case where this "all halt" event has negative
> impact; so please speak up if you are affected.
I'm blocked on fixing click chroot to install
On Fri, 2014-03-21 at 15:08 +0100, Alexander Sack wrote:
> On the front of data, we haven't seen much new. For instance we only
> know about a single case where this "all halt" event has negative
> impact; so please speak up if you are affected.
Generally if you want to know the impact to me you
On Fri, Mar 21, 2014 at 2:17 PM, Oliver Grawert wrote:
> hi,
> Am Freitag, den 21.03.2014, 14:09 +0100 schrieb Alexander Sack:
>
>> >> The TRAINCON levels that were discussed at UDS are:
>> >>
>> >> - TRAINCON-2 - everything green, normal landing rules apply
>> >> - TRAINCON-1 - no promotion for 2
hi,
Am Freitag, den 21.03.2014, 09:26 -0400 schrieb Rick Spencer:
>
> On Fri, Mar 21, 2014 at 9:17 AM, Oliver Grawert
> wrote:
> hi,
> I was suggesting 1.) for this special case. Get out one image
> that
> contains the issue, let users know that it is there and b
hi,
Am Freitag, den 21.03.2014, 14:09 +0100 schrieb Alexander Sack:
> >> The TRAINCON levels that were discussed at UDS are:
> >>
> >> - TRAINCON-2 - everything green, normal landing rules apply
> >> - TRAINCON-1 - no promotion for 2 days, restricted landing rules that
> >> avoids risks and fastpa
Oliver Grawert [2014-03-21 13:36 +0100]:
> I think this is a bug we should treat similar. Instead of killing our
> battery life with a hack, accept that it is there and currently
> unavoidable to have it, document it properly so users know what to
> expect and release one image that passes the test
On Fri, Mar 21, 2014 at 9:17 AM, Oliver Grawert wrote:
> hi,
>
>
> I was suggesting 1.) for this special case. Get out one image that
> contains the issue, let users know that it is there and block further
> promotion of images until we have a fix for the root cause (but keep
> landings going (
On Fri, Mar 21, 2014 at 1:36 PM, Oliver Grawert wrote:
> hi,
> Am Donnerstag, den 20.03.2014, 18:58 +0100 schrieb Alexander Sack:
>> Hi,
>>
>> I am sending this as a proxy for the not-yet existing TRAINCON bot
>> that will give you updates about our touch image alert state that come
>> with indivi
hi,
Am Donnerstag, den 20.03.2014, 18:58 +0100 schrieb Alexander Sack:
> Hi,
>
> I am sending this as a proxy for the not-yet existing TRAINCON bot
> that will give you updates about our touch image alert state that come
> with individual landing rules.
>
> The TRAINCON levels that were discussed
On Friday, March 21, 2014 11:33:35 Alexander Sack wrote:
> Hi,
>
> On Fri, Mar 21, 2014 at 3:23 AM, Scott Kitterman
wrote:
> > On Thursday, March 20, 2014 18:58:28 Alexander Sack wrote:
> >> Hi,
> >>
> >> I am sending this as a proxy for the not-yet existing TRAINCON bot
> >> that will give you
Hi,
On Fri, Mar 21, 2014 at 3:23 AM, Scott Kitterman wrote:
> On Thursday, March 20, 2014 18:58:28 Alexander Sack wrote:
>> Hi,
>>
>> I am sending this as a proxy for the not-yet existing TRAINCON bot
>> that will give you updates about our touch image alert state that come
>> with individual lan
On Thu, Mar 20, 2014 at 10:23:44PM -0400, Scott Kitterman wrote:
> On Thursday, March 20, 2014 18:58:28 Alexander Sack wrote:
> >
> > The bugs that are needed to get fixed are below:
> >
> > * music-app: https://bugs.launchpad.net/music-app/+bug/1292306 (Kevin
> > and Saviq)
> >
> > * alarms:
On Thursday, March 20, 2014 20:30:42 Adam Conrad wrote:
> On Thu, Mar 20, 2014 at 10:23:44PM -0400, Scott Kitterman wrote:
> > On Thursday, March 20, 2014 18:58:28 Alexander Sack wrote:
> > > The bugs that are needed to get fixed are below:
> > > * music-app: https://bugs.launchpad.net/music-app/+
On Thursday, March 20, 2014 18:58:28 Alexander Sack wrote:
> Hi,
>
> I am sending this as a proxy for the not-yet existing TRAINCON bot
> that will give you updates about our touch image alert state that come
> with individual landing rules.
>
> The TRAINCON levels that were discussed at UDS are:
Hi,
I am sending this as a proxy for the not-yet existing TRAINCON bot
that will give you updates about our touch image alert state that come
with individual landing rules.
The TRAINCON levels that were discussed at UDS are:
- TRAINCON-2 - everything green, normal landing rules apply
- TRAINCON-
22 matches
Mail list logo
