<div dir="ltr"><div> </div>Sounds like a good solution to me. </div><div class="gmail_extra"> <div class="gmail_quote">On Wed, Jun 26, 2013 at 7:10 PM, Gema Gomez <<a href="mailto:gema.gomez-solano@canonical.com" target="_blank">gema.gomez-solano@canonical.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hey, Why don't we just add some jobs to jenkins for Daniel to care for/look at? <div class="im"> Sounds like a compromise, Thomi can add them pretty easily then hand </div>them over to Daniel and job done from the mir team's perspective. They <div class="im">don't even need to appear in any dashboard, they can be prefixed with Daniel's name or some other prefix that excludes them from other people's lists. </div>We have some jobs that are for a particular person or need, they are <div class="im">testing something very particular and this doesn't need to be a burden on others. FWIW, Robert, I agree that automation is not always a blessing, automation always comes at a cost, but if Daniel thinks it can help him do something that otherwise is going to cause him (and possibly others) grieve, then I think it may be worth at least trying. </div>Thomi, could we do that? <div class="im"> Just a thought in case it helps, Gema </div><div class="im">On 26/06/13 06:54, Daniel van Vugt wrote: </div><div><div class="h5">> Fair point. So don't CI it and I will wear the burden of owning raring > support, as I already offered to. > > > On 26/06/13 13:53, Robert Ancell wrote: >> This is the important point: if we put this into CI it wont just be your >> time spent - it will be everyone else having to change their branches to >> satisfy a GCC we're not requiring. >> >> --Robert >> >> >> On Wed, Jun 26, 2013 at 5:49 PM, Daniel van Vugt >> <<a href="mailto:daniel.van.vugt@canonical.com">daniel.van.vugt@canonical.com</a> <mailto:<a href="mailto:daniel.van.vugt@canonical.com">daniel.van.vugt@canonical.com</a>>> >> wrote: >> >> Put it this way: I will waste more time waiting for builds on my >> saucy machines, than I spend fixing the raring build failures (so I >> can build on my faster raring machine). >> >> And the fixes so far have been trivial. When they're not, I will >> reconsider where my effort goes. >> >> >> >> On 26/06/13 12:22, Robert Ancell wrote: >> >> I do disagree that increased automation is better. In this >> case our >> target platform is GCC 4.8 and slowing down to fix bugs in GCC >> 4.7 isn't >> a worthwhile use of time. I appreciate there might be cases >> where these >> are genuine bugs that 4.8 is not detecting, but that seems >> more of a >> problem in GCC than our code. Also, it seems highly likely for >> us to use >> a GCC 4.8 feature given we are already using modern C++ features. >> >> --Robert >> >> >> On Wed, Jun 26, 2013 at 2:50 PM, Daniel van Vugt >> <<a href="mailto:daniel.van.vugt@canonical.com">daniel.van.vugt@canonical.com</a> >> <mailto:<a href="mailto:daniel.van.vugt@canonical.com">daniel.van.vugt@canonical.com</a>> >> <mailto:<a href="mailto:daniel.van.vugt@">daniel.van.vugt@</a>__<a href="http://canonical.com" target="_blank">canonical.com</a> >> <mailto:<a href="mailto:daniel.van.vugt@canonical.com">daniel.van.vugt@canonical.com</a>>>> >> >> wrote: >> >> I doubt people would object to increased automation, unless >> we start >> needing language features missing in gcc-4.7. >> >> >> >> On 26/06/13 10:49, Thomi Richards wrote: >> >> Hi Daniel, >> >> >> On Wed, Jun 26, 2013 at 2:32 PM, Daniel van Vugt >> <<a href="mailto:daniel.van.vugt@canonical.com">daniel.van.vugt@canonical.com</a> >> <mailto:<a href="mailto:daniel.van.vugt@canonical.com">daniel.van.vugt@canonical.com</a>> >> <mailto:<a href="mailto:daniel.van.vugt@">daniel.van.vugt@</a>__<a href="http://canonical.com" target="_blank">canonical.com</a> >> <mailto:<a href="mailto:daniel.van.vugt@canonical.com">daniel.van.vugt@canonical.com</a>>> >> <mailto:<a href="mailto:daniel.van.vugt@">daniel.van.vugt@</a> >> <mailto:<a href="mailto:daniel.van.vugt@">daniel.van.vugt@</a>>__<a href="http://cano__nical.com" target="_blank">cano__nical.com</a> <<a href="http://canonical.com" target="_blank">http://canonical.com</a>> >> >> <mailto:<a href="mailto:daniel.van.vugt@">daniel.van.vugt@</a>__<a href="http://canonical.com" target="_blank">canonical.com</a> >> <mailto:<a href="mailto:daniel.van.vugt@canonical.com">daniel.van.vugt@canonical.com</a>>>>> >> >> wrote: >> >> >> Can we add raring CI support back in so these build >> problems get >> caught in time? >> >> >> I believe that's a question for me, and the answer is >> "yes, we can". >> Unless there are any objections, I'll add raring as a >> CI platform >> tomorrow (thereby giving the list 12 hours to object). >> >> >> Cheers, >> >> >> -- >> Thomi Richards >> <a href="mailto:thomi.richards@canonical.com">thomi.richards@canonical.com</a> >> <mailto:<a href="mailto:thomi.richards@canonical.com">thomi.richards@canonical.com</a>> >> <mailto:<a href="mailto:thomi.richards@">thomi.richards@</a>__<a href="http://canonical.com" target="_blank">canonical.com</a> >> <mailto:<a href="mailto:thomi.richards@canonical.com">thomi.richards@canonical.com</a>>> >> <mailto:<a href="mailto:thomi.richards@">thomi.richards@</a> >> <mailto:<a href="mailto:thomi.richards@">thomi.richards@</a>>__<a href="http://canon__ical.com" target="_blank">canon__ical.com</a> <<a href="http://canonical.com" target="_blank">http://canonical.com</a>> >> >> <mailto:<a href="mailto:thomi.richards@">thomi.richards@</a>__<a href="http://canonical.com" target="_blank">canonical.com</a> >> <mailto:<a href="mailto:thomi.richards@canonical.com">thomi.richards@canonical.com</a>>>> >> >> >> -- >> Mir-devel mailing list >> <a href="mailto:Mir-devel@lists.ubuntu.com">Mir-devel@lists.ubuntu.com</a> <mailto:<a href="mailto:Mir-devel@lists.ubuntu.com">Mir-devel@lists.ubuntu.com</a>> >> <mailto:<a href="mailto:Mir-devel@lists.">Mir-devel@lists.</a>__<a href="http://ubuntu.com" target="_blank">ubuntu.com</a> >> <mailto:<a href="mailto:Mir-devel@lists.ubuntu.com">Mir-devel@lists.ubuntu.com</a>>> >> >> Modify settings or unsubscribe at: >> <a href="https://lists.ubuntu.com/____mailman/listinfo/mir-devel" target="_blank">https://lists.ubuntu.com/____mailman/listinfo/mir-devel</a> >> <<a href="https://lists.ubuntu.com/__mailman/listinfo/mir-devel" target="_blank">https://lists.ubuntu.com/__mailman/listinfo/mir-devel</a>> >> <<a href="https://lists.ubuntu.com/__mailman/listinfo/mir-devel" target="_blank">https://lists.ubuntu.com/__mailman/listinfo/mir-devel</a> >> <<a href="https://lists.ubuntu.com/mailman/listinfo/mir-devel" target="_blank">https://lists.ubuntu.com/mailman/listinfo/mir-devel</a>>> >> >> >> > </div></div><div class="im">-- Gema Gomez-Solano <<a href="mailto:gema.gomez-solano@canonical.com">gema.gomez-solano@canonical.com</a>> Ubuntu QA Team <a href="https://launchpad.net/~gema" target="_blank">https://launchpad.net/~gema</a> Canonical Ltd. <a href="http://www.canonical.com" target="_blank">http://www.canonical.com</a> </div><div class="im">-- Mir-devel mailing list <a href="mailto:Mir-devel@lists.ubuntu.com">Mir-devel@lists.ubuntu.com</a> </div>Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/mir-devel" target="_blank">https://lists.ubuntu.com/mailman/listinfo/mir-devel</a> </blockquote></div> </div>