[02:04] <imgbot> [03:04] <imgbot> [03:54] <imgbot> [03:54] <imgbot> [04:19] <imgbot> [04:19] <imgbot> [12:08] <ricmm> bzoltan: so only 107+ ? 106 and 105 clean?
[12:09] <ricmm> bzoltan: basically just want to know if 105 is broken, and if 107 is broken for you then try to roll back to qtdeclarative5-qtmir-plugin to 0.4.3+14.10.20141013-0ubuntu1
[12:10] <bzoltan> ricmm:  yes, up until 106 it was OK and from 107 the UITK AP tests are broken
[12:10] <ricmm> ok
[12:10] <ricmm> in that case its the desktop file reader changes
[12:10] <bzoltan> ricmm:  I have not yet tried to roll back
[12:11] <bzoltan> ricmm: do you know who yo talk for the fix?
[12:12] <ricmm> bzoltan: dandrader, gerry, kgunn
[12:12] <ricmm> but first do confirm with a rollback of qtmir
[12:12] <ricmm> just to make sure the pinpointed version is correct
[12:13] <bzoltan> ricmm: OK, so it is 0.4.3
[12:13] <bzoltan> ricmm:  is it a trival downgrade?
[12:14] <ricmm> bzoltan: apt-get install qtdeclarative5-qtmir-plugin=0.4.3+14.10.20141013-0ubuntu1
[12:15] <bzoltan> ricmm: cool, thank you ... doing it right now
[12:34] <Saviq> davmor2, bug #1383277
[12:35] <popey> ooh, i have been seeing that too
[12:35] <Mirv> bfiller: I published the rtm-002 now.
[12:36] <bfiller> Mirv: thanks, would be great if we could respin a mako image with that
[12:37] <Mirv> bfiller: I'll ping og_ra when it has migrated to release pocket
[12:38] <Mirv> bfiller: I wonder if we should try to get it to utopic too? I'm not sure if those ubuntu-phone thread repliers are using rtm or utopic
[12:39] <bfiller> Mirv: we should probably get it to ubuntu as well, I think the people were using rtm but we should to be safe
[12:39] <popey> Saviq: davmor2 bug 1383279
[12:39] <Saviq> popey, a
[12:39] <Saviq> h
[12:40] <Saviq> popey, reassigned to u-s-c
[12:40] <Mirv> bfiller: ^ that 001 will have it, kicked build button.
[12:46] <bfiller> Mirv: thanks
[12:46] <bfiller> Mirv: could you create silos for line 56 and 57 when you have a chance?
[12:55] <Mirv> ogra_: bill requested ^ above at least mako rtm image build, could you arrange it? the sim unlock problem seen on the mailing list would be now fixed.
[12:56] <ogra_> i cant do a Mako only build
[12:56] <ogra_> but i can indeed trigger an RTM image build
[12:57] <Mirv> ogra_: yeah, that's what I thought. I guess that's important enough bug that it'd be nice to have a new image sooner.
[12:58] <Mirv> hmm, I guess sil2100 is still stuck somewhere in Frankfurt or so :(
[12:58] <ogra_> right, no issue with that
[12:58] <ogra_> yup, i just saw his mail ... i think his new filght is in 2-3h
[12:59] <ogra_> ... "I'm stuck here until the flight at 17:00 UTC+2" ...
[12:59] <ogra_> even more
[12:59] <Mirv> he didn't mail me, but I heard yesterday evening
[12:59] <Mirv> that's terrible
[12:59]  * ogra_ is on the right MLs :) 
[13:00] <Mirv> ogra_: argh, not again... "aren't you on the xyz mailing list"
[13:00] <ogra_> obviously LH screwed up his re-booking
[13:00] <Mirv> I wonder if I should be on some more lists..
[13:00] <ogra_> Mirv, thats the internal foundations list ... i was on that team and didnt unsubscribe when i changed :)
[13:00] <Mirv> hehe, right
[13:03] <Saviq> jdstrand, hey, could we get your feedback on bug #1383086 please (also, is there a project we could add a task for to request security feedback?)
[13:37] <kenvandine> does anyone know why some autopkgtests aren't running?
[13:37] <kenvandine> i have ubuntu-system-settings in proposed and excuses says there is a test running
[13:37] <kenvandine> but it isn't... last run was a week ago
[13:44] <pete-woods> trainguards: if I want to change my mind about the target of my landing (I want to do utopic, rather than rtm), what's the right way to do this?
[14:10] <Mirv> pete-woods: you tell the line number and we'll change it :)
[14:10] <Mirv> or I will, robru being at his home timezone and sil2100 stuck on Frankfurt airport...
[14:10] <Mirv> pete-woods: so, I'd free up the rtm silo and assign utopic one instead
[14:11] <kenvandine> Mirv, do you know why we have a bunch of packages stuck in proposed?
[14:11] <kenvandine> Mirv, excuses says "test running"
[14:12] <kenvandine> but they aren't running :)
[14:12] <Mirv> kenvandine: in rtm or utopic?
[14:12] <kenvandine> utopic
[14:12] <Mirv> oh..
[14:12] <kenvandine> we have packages stuck migrating since friday
[14:14] <Mirv> the answer to your question is "no" (do I know). we should probably ping pitti or someone else.
[14:18] <cjwatson> ask on #ubuntu-release about such things.
[14:19] <pete-woods> Mirv: yes, that would be awesome :)
[14:22] <popey> [D/query balloons
[14:22] <popey> oops
[14:36] <Saviq> Mirv, could we please have a silo for line 42 then, cleaned the utopic-targeted silo ↑
[14:57] <brendand> marcustomlinson, hey
[14:58] <marcustomlinson> brendand: hey
[14:58] <brendand> marcustomlinson, can we sit for a few minutes and look at your silo?
[14:58] <marcustomlinson> brendand: yeah ok
[14:58] <brendand> marcustomlinson, dallas right?
[14:58] <marcustomlinson> brendand: yep
[15:01] <Saviq> Mirv, http://www.markshuttleworth.com/archives/1425
[15:02] <AlbertA> trainguards: line 28 (rtm landing-001) is ready for QA but it's not showing up in the trello queue any ideas?
[15:13] <Mirv> pete-woods: the line number, please? :)
[15:14] <Mirv> Saviq: on time, great!!
[15:14] <Mirv> cjwatson: is vivid open yet? ;)
[15:14] <pete-woods> Mirv: line 62
[15:15] <Mirv> pete-woods: oh right it didn't even have an assigned silo. ok then, 016.
[15:18] <pete-woods> Mirv: sorry, that's a new line. the original one is 49
[15:19] <Mirv> pete-woods: thanks, freed the silo
[15:20] <Mirv> (the line 49)
[15:20] <bzoltan> ogra_: sir, where are you?
[15:20] <Mirv> Saviq: rtm-015
[15:20] <ogra_> bzoltan, hmm, i thinnk its is called ballromm B
[15:21] <cjwatson> Mirv: no :)
[15:24] <popey> davmor2: bug 1383343
[15:24] <popey> dunno if we have one already filed for that, seems we should
[15:26] <davmor2> popey: confirmed
[15:33] <popey> davmor2: ta
[16:25] <brendand> bzoltan, silo 13 isn't going to land this week you know
[17:10] <robru> Mirv: are you at the sprint?
[17:12] <robru> I'm around for any landing needs anybody might have
[17:32] <rsalveti> davmor2: I got a silo that's ready for qa to sign it off, but it seems the spreadsheet is not showing that
[17:32] <rsalveti> rtm silo 14
[17:45] <rsalveti> Saviq: hey, we want to land https://code.launchpad.net/~mfrey/unity8/lock-fix/+merge/238918
[17:45] <rsalveti> Saviq: don't think we're landing more stuff into utopic anymore, so how to proceed with that landing?
[17:45] <Saviq> rsalveti, I'm releasing trunk into rtm
[17:45] <Saviq> rsalveti, I've a silo already, will take that in
[17:46] <rsalveti> Saviq: awesome
[17:47] <robru> rsalveti: fixed spreadsheet status of row 48
[17:47] <rsalveti> robru: thanks!
[17:48] <robru> there it is ;-) you're welcome!
[17:48] <brendand> AlbertA, which bug is silo 17 meant to fix?
[17:48] <brendand> AlbertA, i don't see one mentioned in the changelog
[17:49] <AlbertA> brendand: https://bugs.launchpad.net/media-hub/+bug/1378311
[17:50] <brendand> AlbertA, that's not going to land this week though
[18:00] <AlbertA> brendand: I believe it was indirectly associated with a bug that was tagged 10-23
[18:00] <AlbertA> brendand: but let me check...
[18:07] <Mirv> robru: yes!
[18:07] <robru> Mirv: mmmm, how was the flight? /me is super jealous i didn't get to go
[18:08] <Mirv> robru: yes, it's nice to have you around, since I'm walking around so much that my response time can vary.
[18:08] <Mirv> robru: 1h late (+1.5h US customs queueing), but not too bad especially given how Lukasz is doing.
[18:08] <Mirv> I was here at 10pm, which was ok.
[18:09] <robru> yeah I saw lukasz' email, that's just brutal
[18:11] <ogra_> something he cal tell his kids about :)
[18:11] <ogra_> *can
[18:12] <brendand> bzoltan, ping
[18:12] <brendand> ogra_, what happened?
[18:13] <ogra_> brendand,
[18:13] <ogra_> oops
[18:13] <ogra_> brendand, his original flight was overbooked and they screwed up the new booking
[18:13] <ogra_> he should be in the air now (finally)
[18:16] <robru> ogra_: landings are open, right? I can publish that? ^
[18:17] <ogra_> robru, i donkt think landings are open, no
[18:17] <robru> hm, rsalveti published himself ;-)
[18:17] <ogra_> but thats the sim lock fix, that has been discussed before ...
[18:18] <rsalveti> yeah
[18:18] <ogra_> (talking about rtm-008 and rtm-006)
[18:18] <ogra_> not sure about the mess rsalveti made with rtm-002
[18:18] <ogra_> :P
[18:18] <ogra_> :)
[18:18] <rsalveti> it is ricmm's fault
[18:18] <ogra_> as usual !!
[18:19] <ogra_> robru, we actually planned to build an image once the 006 and 008 packages landed commpletely
[18:20] <robru> ogra_: 6 and 8 aren't even started to publish yet, are they being reviewed still?
[18:20] <ogra_> hmm, dunno, i thought Mirv had handled them this morning already
[18:21] <ogra_> though i'm not sure if anything is allowed to land without QA signing off ... brendand ^^ ?
[18:21] <robru> ogra_: unless they landed already and there's already two new landings in those silos? ;-)
[18:22] <ogra_> magically with the same packages ? :)
[18:22] <Mirv> ogra_: didn't sil write on Friday "This also means we will be unblocking landings through the CI Train now."?
[18:22] <brendand> ogra_, no
[18:22] <Mirv> ogra_: yes I published the mako sim unlock silo
[18:22] <ogra_> Mirv, well, i think olli still only wanted landings for the critical bugfixes
[18:22] <robru> yeah I read something about how landings were unblocked but since it's final freeze it's basically only critical fixes anyway
[18:22] <ogra_> Mirv, and i think every landing needs QA signoff at this point in the release
[18:23] <olli> Mirv, ogra_ is right
[18:23] <olli> i.e. if on the list, good to land
[18:23] <Mirv> ogra_: yes, only rtm14 critical of course
[18:23] <olli> if not, then escalation to product team
[18:23] <ogra_> olli, modulo QA signoff indeed :)
[18:23] <olli> for exception
[18:23] <ogra_> sine we want to keep brendand and davmor2 busy ;)
[18:23] <Mirv> both today's fixes so far were for 2014-10-23 critical ones
[18:23] <ogra_> *since
[18:24] <Mirv> ogra_: right, so QA signoff simply to every landing..
[18:24] <ogra_> yeah
[18:24] <Mirv> ricmm: that means I'm changing your "turn off backlight" silo to also requiring signoff
[18:24] <ogra_> Qa might decide the landing is trivial enough to just let it through, but we should get their comment at least
[18:24] <Mirv> and ken's system-settings and pete-woods's silo
[18:24] <ogra_> Mirv, a bit late :P
[18:25] <Mirv> oh...
[18:25] <ogra_> (given it is already migrating)
[18:25] <ricmm> :)
[18:25] <Mirv> right :)
[18:25] <olli> Mirv, checking the tags only is not sufficient
[18:25] <olli> as anyone can set the tags and sometimes they get set by accident
[18:26] <Mirv> and Saviq's unity8 landing
[18:26] <olli> the list from my mail is the authoritive source
[18:26] <ogra_> well, only landing team should set them ... (though indeed everyone can set them, the landing team simply needs to check twice)
[18:26] <Mirv> olli: right.. so the 10/16 email. check.
[18:27] <olli> Mirv, 10/23 ;)
[18:27] <Mirv> olli: yes, 10/23 email sent on 10/16 :)
[18:27] <olli> hah
[18:27] <olli> I can see now how this gets confusing
[18:28] <Mirv> Saviq: so, I can immediately see your unity8 landing has bugs listed not on the List, so they should be escalated if wanted in
[18:30] <rsalveti> but we're not just accepting MRs for the bugs from that email
[18:30] <rsalveti> afaik we're back in the game and landing criticals
[18:30] <rsalveti> even if not for this deadline
[18:31] <davmor2> ogra_: I'm so going to slap you into the middle of next month
[18:31] <Mirv> rsalveti: reading olli above it sounds like only bugs from the e-mail, or would need contacting the product team
[18:31] <rsalveti> doesn't make sense, we had that for one week only, for the purpose of that milestone
[18:31] <rsalveti> olli: isn't that the case?
[18:32] <ogra_> rsalveti, as i understood we only land what has been approved by olli, pmcgowan or vicotr ... and then only after QA signed it off
[18:32] <rsalveti> as we're fixing the other critical bugs, and we want to land them
[18:32] <rsalveti> ogra_: I thought that was only for the previous milestone
[18:32] <olli> rsalveti, only what's on the list for 10/23
[18:32] <ogra_> (heh, vicotr ... victors evil russian brother)
[18:32] <rsalveti> olli: why that?
[18:32] <rsalveti> why did we decide to push the same requirements for 23?
[18:33] <olli> rsalveti, ideally, we shouldn't fix bugs that aren't on the list, unless the list is wrong or there is a good opportunity
[18:33] <rsalveti> olli: well, we have people enough to fix some other criticals
[18:33] <rsalveti> same that happened last week
[18:33] <ogra_> rsalveti, the bugs simply need to be sent to either of these three and be added to the list
[18:33] <Mirv> yes, that's what Saviq said too, they have more people than bugs on the list
[18:33] <rsalveti> we're just flushing them now
[18:33] <rsalveti> ogra_: right, I don't understand why we need that
[18:33] <Mirv> it does make sense to fix later critical bugs earlier
[18:33] <rsalveti> we have the rtm14 bug list
[18:33] <rsalveti> exactly
[18:33] <olli> rsalveti, the intention is to reduce churn & regression risk
[18:34] <rsalveti> if it's on the rtm14 critical list, let's land it
[18:34] <ogra_> rsalveti, because they want to asses the risk for their product
[18:34] <rsalveti> olli: but them we'll never fix every bug
[18:34] <rsalveti> it's just a waste of time
[18:34] <rsalveti> we should land every critical we have now
[18:34] <rsalveti> as before
[18:34] <rsalveti> anytime
[18:34] <nik90> olli: is the rtm14 critical list public? Since I need to check if some alarm bugs are on that list which would affect user experience.
[18:34] <rsalveti> we can't land on utopic, can't land criticals out of that list
[18:34]  * ogra_ doesnt care either way, i just know what was requested
[18:34] <rsalveti> will just take vacations
[18:35] <ogra_> in any case everything going into RTM needs QA signoff ... regardless of the list
[18:35] <Mirv> nik90: https://bugs.launchpad.net/bugs/+bugs?field.tag=rtm14
[18:35] <olli> rsalveti, let's chat in the break
[18:35] <rsalveti> olli: sure
[18:35] <olli> rsalveti, vacation or improve test coverage or ...
[18:35] <rsalveti> but I'm in favor of always landing critical fixes, sooner the better
[18:35] <ogra_> olli, there are a good bunch of bugs that wont affect krillin but mako ... which we definitely want tto have fixed
[18:36] <olli> rsalveti, I'd be with you if the overall number of bugs would go down
[18:36] <nik90> Mirv: and If I need to request a bug to be on that list, do I ask olli and victorp?
[18:36] <rsalveti> olli: but that's because we still have bugs
[18:36] <rsalveti> ignoring that is just ignoring the reality that we have more bugs
[18:36] <Mirv> nik90: so basically any bug that both has the tag "rtm14" and is Critical. then we have an these "touch-2014-10-23" milestones additionally, and this List we're talking about is about those subsets of the whole list
[18:36] <rsalveti> the bug number will still increase for a while
[18:36] <rsalveti> until it's stable
[18:36] <rsalveti> we now have way more people using the product
[18:36] <rsalveti> expect more bugs
[18:36] <nik90> Mirv: ok
[18:37] <Mirv> ogra_: what was the policy on adding 'rtm14' tag itself?
[18:37] <ogra_> uh, i forgot
[18:37] <bzoltan> brendand: pong
[18:37] <Mirv> yeah, me too :P
[18:37] <ogra_> heh
[18:37] <ogra_> sil might know
[18:37] <rsalveti> I just think we'll never ship if we keep this process as is
[18:38] <rsalveti> but anyway, will complain in the corridor
[18:38] <olli> :)
[18:38] <Mirv> nik90: well, for now contact me or sil2100 when you've a bug that is critical (that part you can set yourself in your own projects) and that would also like to have the 'rtm14' tag.
[18:38] <bzoltan> brendand:  Is it because of the UITK or is there a generic freeze?
[18:38] <nik90> Mirv: ack
[18:38] <olli> Mirv, rtm14 is for you to express that this is relevant for the product
[18:38] <rsalveti> we're only landing ones that already has a deadline, just not for 23
[18:38] <Mirv> nik90: ^ ok there you go, you can add rtm14 for your own project when you think it should be in the radar as a critical bug
[18:39] <Mirv> olli: thanks.
[18:39] <bzoltan> elopio:  the AP failures are same with the   qtdeclarative5-qtmir-plugin:armhf                    0.4.4+14.10.20141013-0ubuntu1
[18:39] <rsalveti> postponing something that was originally for 30 just because we can't include it for 23 makes no sense
[18:39] <rsalveti> made sense last week because of the reason of the deadline
[18:39] <pmcgowan> rsalveti, you can, if its rtm and crit
[18:40] <rsalveti> pmcgowan: olli said I can only land stuff on the 23 list
[18:40] <pmcgowan> ok go yell at him then :)
[18:40] <elopio> bzoltan: do you mean, the same +70 errors?
[18:40] <Mirv> I think that was the plan :)
[18:40] <rsalveti> pmcgowan: that's what I'm doing here
[18:40] <rsalveti> :-)
[18:40] <olli> pmcgowan, hey...
[18:41] <brendand> bzoltan, the landings are restricted to ollis list
[18:41] <bzoltan> elopio:  yes
[18:41] <pmcgowan> heh olli's list
[18:41] <bzoltan> elopio:  I have flashed the 118 image and downgraded that package.
[18:44] <bzoltan> brendand:  Well, obviously  I am not happy for it. But can not do much I guess. I hope that the V queue will soon open and I can start landing there.
[19:20] <ogra_> Mirv, so what about the SIM lock stuff ? i cant see it on the dashbaodr
[19:20] <ogra_> wow, what a typo
[19:21] <ogra_> Mirv, i would actually like to trigger an image build ( rsalveti wants one too) ... but i cant seem to find the SIM lock issue landing anywhere
[19:23] <ogra_> ah, found it ... line 39 ... and it actually landed
[19:23]  * ogra_ triggers a build 
[19:23] <ogra_> imgbot, stunt
[19:23]  * imgbot rolls on its back and purrs
[19:23] <ogra_> good :)
[19:24] <olli> lol
[19:25] <cjwatson> bzoltan1: Friday, hopefully
[19:26] <bzoltan1> cjwatson:  Friday is good, thanks
[19:26] <cjwatson> not promising but we've managed to be up and running within a day of release before ...
[19:27] <bzoltan1> sure, I totally understand
[19:29] <imgbot> [19:32] <Mirv> ogra_: yes, thanks!
[19:33] <Saviq> Mirv, there actually *is* a DO_NOT_ADD_RTM option ;)
[19:34] <Mirv> Saviq: oh, right, it is there!
[19:34] <ogra_> WHY_DO_ALL_OPTIONS_SCREAM ?
[19:34] <Saviq> ogra_, BECAUSE_THEYRE_IMPORTANT
[19:35] <ogra_> AH_THAT_MAKES_SENSE_THEN
[20:27] <robru> bzoltan: row 70 is missing something
[20:27] <Mirv> robru: oops :) I added it
[20:28] <Mirv> we're rapidly trying to get the MR in there. sorry for setting it as "Ready"
[20:28] <Mirv> the battle for working wifi
[20:31] <robru> Mirv: heh, no worries.
[20:32] <bzoltan> robru: Mirv: ready :)
[20:33] <robru> bzoltan: Mirv utopic 14
[20:37] <Mirv> bzoltan: building https://ci-train.ubuntu.com/job/ubuntu-landing-014-1-build/81/console
[20:38] <Mirv> zbenjamin: conflicts
[20:39] <imgbot> [20:39] <imgbot> [20:39] <ogra_> wow
[20:39] <robru> pete-woods: ^ I'm afraid to publish anything as I've been out for 2 weeks. what's up with silo 16?
[20:39] <ogra_> that was really fast !
[20:40] <robru> hm
[20:40] <davmor2> ogra_: that just means it didn't work and we now all have broken images right?
[20:40] <ogra_> davmor2, well, blame rsalveti :P
[20:41] <davmor2> rsalveti: it's all you fault!!!!
[20:41] <kenvandine> davmor2, why can't it ever be your fault? :-p
[20:42] <robru> wtfqueuebot
[20:42] <davmor2> kenvandine: it is but most that I let stuff through that was broken by the devs :P
[20:42] <Mirv> oh, not again, the 1min repeat queuebot thing
[20:42] <ogra_> it *relly* wants to publish that :)
[20:42] <ogra_> *really
[20:42] <kenvandine> really
[20:42] <robru> but but!
[20:42] <robru> I remember the cause of that issue and the spreadsheet doesn't look like it has that problem right now!
[20:42] <Mirv> it became fun when it was repeating three different landings every minute
[20:44] <pete-woods> robru: I think it's ready (I mean I've tested it). but I don't know the rules about publishing..
[20:44] <robru> pete-woods: is it a critical bugfix? utopic is in final freeze ;-)
[20:45] <pete-woods> robru: it is, yes
[20:45] <robru> pete-woods: ok
[20:46] <ricmm> :)
[20:46] <ricmm> s'il vous plait
[20:47] <robru> ricmm: rtm 2
[20:47] <ricmm> robru: thanks
[20:47] <robru> ricmm: you're welcome
[20:57] <davmor2> ogra_, rsalveti: why is this image never seeming to finish flashing?
[20:58] <davmor2> ogra_, rsalveti: nevermind it just finished but my god that took a while :)
[20:58] <rsalveti> davmor2: hahah
[20:58] <rsalveti> I might be able to flash it tomorrow, will take a while to download it
[20:58] <rsalveti> really slow
[21:00] <cwayne> davmor2, got time for a custom tarball test tomorrow?  only critical bug fixes I swear :)
[21:00] <robru> somebody who knows stuff let me know if it's actually ok to publish silo rtm 14
[21:00] <davmor2> cwayne: Where's my fitbit damn you ?  possibly depends when
[21:00] <robru> or not
[21:01] <Mirv> robru: yes, I just published it. so it is on the 10/23 List (on the mailing list), ie ok.
[21:01] <robru> ah ok, thanks Mirv
[21:01] <Mirv> "10/23 iteration planning"
[21:01] <cwayne> davmor2, its in my room
[21:02] <cwayne> i dont have a charger for it though :/ but i do have the dongle to sync it
[21:05] <balloons> ogra_, https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1383479
[21:05] <ogra_> olli, pmcgowan ^^^ we need to talk about this one
[21:08] <olli> ogra_, ack, not sure I fully grasp the implications
[21:19] <pmcgowan> ogra_, yeah, this week or next?
[21:21] <pmcgowan> balloons, ^^?
[21:26] <pmcgowan> ogra_, balloons although if it has a small footprint I suppose there is not so much urgency?
[21:33] <ogra_> pmcgowan, it has a giant dependency chain
[21:33] <ogra_> (it will remove quite a bit of python packages)
[21:33] <pmcgowan> that sounds good
[21:34] <pmcgowan> so we should do next two weeks
[21:34] <ogra_> pmcgowan, but there is some risk in it, if people dont use out tools for testing but directly call autopilot for example
[21:34] <ogra_> so we should do it early to asess possible fallout
[21:34] <pmcgowan> ogra_, who might do that?
[21:34] <pmcgowan> ok
[21:34] <ogra_> pmcgowan, well, i know that the unity8 team calls AP directly during developemnt
[21:35] <ogra_> (eaiser than always calling pahblet-test-run if you develop )
[21:35] <pmcgowan> ogra_, so maybe an email to the list to prep folks
[21:54] <balloons> pmcgowan, thanks for commenting on it. Sorry, I was offline and missed the discussion
[21:54] <balloons> ogra_, pmcgowan, the potential issues also arise from people depending on autopilot or a dependency without declaring it. It's unlikely but possible