[07:03] <vila> sergiusens: (Too bad you're not there :-/) This should be fixed now (known issue, see .... damn it forgot to hit enter while chasing the url :-/ https://wiki.canonical.com/UbuntuEngineering/CI/IncidentLog/2014-01-11-otto-stop-no-name
[07:03] <vila> fginther: see above /me hides under a rock
[08:02] <sil2100> Morning!
[08:02] <sil2100> hm, brb, modem reboot
[08:38] <sil2100> Hi guys, do we know if the Terminal App keyboard-not-working bug is being targetted by anyone?
=== jodh` is now known as jodh
[09:02] <sil2100> didrocks: morning!
[09:02] <didrocks> sil2100: good morning!
[09:03] <sil2100> didrocks: I just noticed that you're using a strange date for the landing team updates ;)!
[09:03] <didrocks> really?
[09:03] <sil2100> didrocks: 09.11.14 and 10.11.14 ?
[09:03] <didrocks> ah, yeah ;)
[09:03] <didrocks> thanks, will fix in the next one :)
[09:03] <sil2100> Looks like future to me! ;)
[09:04] <didrocks> heh, indeed ;)
=== ev changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: ev | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: -
[09:31] <sil2100> didrocks: I'll be right on
[09:32] <didrocks> sil2100: waiting for you, tell us when you won your battle with hangouts ;)
[09:44] <ogra_> xnox, can you a) merge back your autopilot changes to trunk and b) please use a landing spreadsheet antry next time so stuff like http://people.canonical.com/~ogra/touch-image-stats/20140110.1.changes doesnt happen (and we dont have broken images over the weekend)
[09:46] <ogra_> (note the gigyntic amount of new packages)
[09:46] <ogra_> *gigantic
[09:51] <didrocks> ogra_: are you going to revert the seed change so that we don't install python3-autopilot on the image?
[09:52] <didrocks> (I'm not sure why we have python-autopilot as well installed on the image, we shouldn't)
[10:59] <sil2100> didrocks: regarding that platform-api, qtubuntu and unity-mir - it indeed seems like one merge is still not in, so I guess the feature is not ready for release
[11:00] <didrocks> sil2100: ok, just comment on the landing spreasheet please
[11:00] <didrocks> on the PENDING as well, it was written ready when it wasn't
[11:27] <ogra_> didrocks, it was no seed change (sorry, had some network issues at home) but a dependency change in autopilot
[11:27] <didrocks> ogra_: yeah, I saw that after the fact. We should look at why this metapackage is installed by default though
[11:28] <ogra_> oh. you mean we should drop autopilot-touch altogether ?
=== MacSlow is now known as MacSlow|lunch
[11:29] <ogra_> didrocks, http://paste.ubuntu.com/6744101/
[11:29] <ogra_> seems we carry it sinca august
[11:29] <ogra_> *since
[11:30] <didrocks> ogra_: in your meeting, can you ask more info from rsalveti? Not sure I'm understanding why exactly
[11:30] <didrocks> (I guess we can still have an issue if utah doesn't install it automatically, but that's something we need to check)
[11:30] <ogra_> most likely because the package isnt installable even in rw mode i guess
[11:30] <didrocks> oh, the udev perm
[11:30] <didrocks> IIRC, we add a user
[11:30] <ogra_> (there are some that bail on the dpkg hardlinks)
[11:31] <ogra_> oh, right and the udev rule
[11:31] <ogra_> probably rather that than hardlinks
[11:31] <didrocks> ok, we know why, still that one to figure out then :)
[11:31] <ogra_> will carry it to the meeting (but leave it seeded for now)
[11:31] <didrocks> sounds legit, thanks ogra_!
[11:33] <ogra_> didrocks, do you want to revert xnox' dependency change (i think if you just build from trunk it will be reverted)
[11:34] <didrocks> ogra_: no, let's wait for xnox to backport his change to trunk rather
[11:34] <ogra_> ok, so we keep all these python packages in the image
[11:34] <didrocks> ogra_: I don't have opinions and we'll need to drop all this from the image anyway (all autopilot)
[11:34] <didrocks> yeah, that makes "this issue" even more visible for now :p
[11:34] <ogra_> oh. ok
=== alan_g is now known as alan_g|afk
[12:16] <sergiusens> didrocks, ogra_ the reason it's preinstalled is to allow people to test click without going into rw
[12:16] <ogra_> yeah, i thought it was click related ... the commit message isnt so explicit
[12:16] <didrocks> sergiusens: would be nice to find another way (or a simple switch to go into rw for them)
[12:17] <Mirv> ev: qa-intel-4000 is offline
[12:17] <didrocks> we are installing dozen of package for testing in our product, doesn't make sense
[12:17] <sergiusens> didrocks, if you go into read write and install dependencies you will never know if the system in ro mode would work though
[12:17] <Mirv> I noticed it had had a kernel crash and a job was seemingly hanged, so I aborted it after which I got the report it's now offline
[12:17] <didrocks> sergiusens: well, it's the same issues than for all the other tests TBH
[12:18] <sergiusens> didrocks, yeah, I was hoping for QA to get us a path out of there
[12:18] <didrocks> sergiusens: but I don't think it makes sense to ship autopilot in the image just for that
[12:18] <didrocks> yeah
[12:18] <sergiusens> it's not a good situation
[12:18] <didrocks> sergiusens: adding a note for it, we need to fix that before 14.04
[12:19] <sergiusens> I asked for a self contained non deb autopilot once iirc
[12:19] <didrocks> that can be a solution
[12:20] <Mirv> ev: and it's up again, maybe an automagic recovery
=== MacSlow|lunch is now known as MacSlow
[12:44] <psivaa> didrocks: maguro tests with r125 just completed: http://ci.ubuntu.com/smokeng/trusty/touch/maguro/125:20140113:20140107.1/6035/
[12:46] <davmor2> psivaa: I've found an issue on the maguro post mir update, apps are hanging again so I'm not sure how much that is effecting results
[12:46] <davmor2> didrocks: ^
=== alan_g|afk is now known as alan_g
[12:47] <Saviq> ev, hey, there's something weird in  http://naartjie/archive//head.unity8/ - there's a libunity-mir-dev 0.2+14.04.20140108.1bzr168pkg0trusty0-0ubuntu1, where lp:unity-mir only has 162 revs?
[12:48] <davmor2> didrocks: I'm going to be digging into it a bit more latter today if all goes well, but I discovered it testing on friday for balloons fix for calendar
[12:51] <didrocks> psivaa: thanks!
[12:51] <didrocks> davmor2: can you give a little bit more details? And give them to kgunn?
[12:53] <davmor2> didrocks: didn't get much time to dig into it friday hence hoping to today once I have more info I will gladly pass it on,  I'm going to run a bunch of test from the coreapps ppa and see what fails where and why and then create a bug based on that info
[12:53] <didrocks> thanks
[12:53] <didrocks> davmor2: this is from an older image, right? Since the Mir update? (so rev 119 or so)
[12:54] <davmor2> didrocks: yeah friday afternoon so 121 iirc
[12:57] <didrocks> davmor2: Mir isn't new in 121, was it?
[12:57] <sil2100> didrocks: the evernote project is ok for preNEWing I guess, I added this MR to finish up some small things: https://code.launchpad.net/~sil2100/account-plugin-evernote/misc_and_bootstrap/+merge/201384
[12:57] <sil2100> (missing bootstrap in changelog)
[12:58] <didrocks> sil2100: ok, reviewing at length at the same time
=== alan_g is now known as alan_g|lunch
[12:58] <davmor2> didrocks: no but it is when I hit the issue running tests, I think the new mir landed earlier in the week and we noticed issues on maguro from then
[13:00] <davmor2> didrocks: I can dig into when the new mir landed and see if I can still get that image and run against it, But I'm assuming I won't be able to
[13:01] <didrocks> davmor2: it's the image just before IIRC, would be nice to ensure you are getting the issue on that one
[13:03] <davmor2> didrocks: no problems
=== josepht changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: josepht | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: -
[13:15] <sil2100> didrocks: strange, I can't globally approve it as well - I can only change the status to 'Merged', there's no 'Approved' o_O
[13:15] <sil2100> didrocks: which is strange, since I thought that when we're not added we cannot change the merge status in overall
[13:16] <didrocks> sil2100: I guess you can mark it manually as merged as you are the branch owner
[13:16] <didrocks> even if you don't have the rights to approve it
[13:18] <sil2100> didrocks: ah, makes sense
=== alan_g|lunch is now known as alan_g
[13:40] <sil2100> didrocks: could you approve the invite of ubuntu-unity to be part of reminders-app-dev ? ;)
[13:40]  * sil2100 poked Mirv to add us there
[13:41] <didrocks> sil2100: done
[13:41] <sil2100> didrocks: thanks! Approved the merge now
[13:42] <didrocks> great ;)
[13:50] <timp> I got a unity8 crash here. Any ideas why? https://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-mako/4625/
[13:51] <timp> greyback: ^?
[13:53] <greyback> timp: think mir failed on startup, I see "what():  error during hwc set()" which causes crash
[14:08] <timp> hmm - I see something similar in another MR https://code.launchpad.net/~nicolas-doffay/ubuntu-ui-toolkit/fix-1240019/+merge/199312
[14:25] <asac> didrocks: so are the failures on unity8/notes/rssreader flaki or hard regressions?
[14:25] <asac> http://ci.ubuntu.com/smokeng/trusty/touch/mako/125:20140113:20140107.1/6032/
[14:25] <didrocks> asac: notes/rss -> flaky, still the same
[14:25] <didrocks> see my previous emails
[14:25] <didrocks> and unity8, regression due to pygi
[14:25] <didrocks> look at #ubuntu-touch and #ubuntu-unity
[14:25] <asac> didrocks: ok we stop the line for that, right?
[14:25] <didrocks> yep
[14:25] <asac> ok good.
[14:26] <didrocks> upstream issues, not sure why pitti doesn't revert the faulty upstream release
[14:26] <didrocks> at least, there is a workaround for it and unity8 is implementing it
[14:26] <asac> didrocks: workaround or fix?
[14:27] <didrocks> workaround
[14:27] <asac> didrocks: have you explained pitti that we now do a workaround?
[14:27] <didrocks> see bug #1268578
[14:27] <ubot5> bug 1268578 in pygobject (Ubuntu) "Notification callback causes exception in gi" [High,Triaged] https://launchpad.net/bugs/1268578
[14:27] <asac> have you asked him if we couldnt back this out rather than doing a workaround?
[14:27] <didrocks> he suggested the workaround
=== vrruiz_ is now known as rvr
[15:29] <ev> Saviq: did you get a response to your query about naartjie? Sorry, I was at lunch when you asked.
=== vrruiz_ is now known as rvr
=== alan_g is now known as alan_g|tea
[15:50] <rsalveti> didrocks: when are we integrating another mir revision?
[15:50]  * rsalveti wants the nexus 7 fix
[15:51] <didrocks> rsalveti: we didn't get any sign since Thursday, so when they are ready. Note that davmor2 is investigating a Mir-related potential regression, so we need more infos on that first
[15:51] <didrocks> davmor2: did you open a bug about it btw? will  be easier to track
[15:51] <rsalveti> didrocks: right, need to ping someone from the mir team then
[15:52] <rsalveti> didrocks: who usually request a mir landing, kgun?
[15:52] <davmor2> didrocks: I was looking into it more first but being as it is on maguro will you care any more ? :)
=== alan_g|tea is now known as alan_g
[15:52] <didrocks> rsalveti: indeed, kgunn
[15:52] <rsalveti> davmor2: no, we want a fix still
[15:52] <rsalveti> we'll drop it soon, but we want to have it supported until we officially drop it :-)
[15:53] <rsalveti> and have one last stable image supported by UE
[15:53] <rsalveti> before we move to community
[15:53] <davmor2> rsalveti: no worries then I'm assuming it is a memory issue which hangs the app on start up but hadn't had chance to dig any yet
[15:53] <rsalveti> alright
[15:54] <davmor2> so a mix of memory and gfx possibly
[15:55] <davmor2> rsalveti: when running some tests for balloons I basically got this http://ubuntuone.com/2ixQVLJb711JUr5m7OLXpB
[15:55] <rsalveti> davmor2: hm, weird
[15:56] <rsalveti> davmor2: anything useful in syslog/logcat?
[15:57] <davmor2> rsalveti: not that I could see but after I'm going to do a fresh install so the logs are mint and try running the test again so if there are any issues they stand out more
[15:58] <davmor2> but again it was late friday for me so didn't get to dig too much, I'm just clearing down the last of the apps for today and then dealing with this for the rest of the day
[16:03] <rsalveti> davmor2: right, let me know if you're able to reproduce it again
[16:04] <davmor2> rsalveti: should be able too what logs are useful to you and I'll grab the lot,  the test is against calendar so I'm assuming ~/.cache/upstart/calendar.log and /var/log/syslog anything else?
[16:06] <rsalveti> davmor2: /system/bin/logcat as well (run as root)
[16:06] <davmor2> rsalveti: will do
[16:44] <didrocks> sergiusens: hey, can you ensure latest notes-app will be soon in the archive (deb side is fine)
[16:44] <sergiusens> didrocks, sure, let me do that now
[16:46] <didrocks> sergiusens: also, can you fix usensord to be priority optional?
[16:47] <didrocks> sergiusens: I wrote that on the landing spreadsheet for robru, but I guess he missed it…
[16:47] <sergiusens> didrocks, yup
=== gatox is now known as gatox_lunch
[16:47] <didrocks> thanks ;)
[17:00] <sil2100> Meeting time!
[17:01] <didrocks> robru: ogra_: coming?
[17:01] <ogra_> nope :P
[17:06] <davmor2> rsalveti: hmmm this is interesting on a fresh install the tests are running fine that failed on friday, so I'm wondering if it was the fact that I had accounts setup apps installed etc that was breaking stuff so I'll add some data to the phone and try it again then look at what changed between the images
[17:09] <kenvandine> sil2100, don't rerun the webcred stack until this is merged https://code.launchpad.net/~ken-vandine/libaccounts-glib/no_libtool_bin/+merge/201439
[17:09] <sil2100> kenvandine: sure :)
[17:10] <kenvandine> the ppa build will block forever without it
[17:13] <sil2100> plars: ^ regarding the jenkins unblocking for webcreds
[17:13] <kenvandine> sil2100, merged
[17:13] <sil2100> plars: ^ nevermind!
[17:13] <sil2100> kenvandine: thanks for the info!
[17:13] <kenvandine> :)
[17:13] <kenvandine> np
[17:14] <plars> sil2100: I was just talking to fginther about it, not sure why that file is missing, but it is indeed missing. Any chance it was just missing because of the other breakage?
[17:15] <sil2100> plars: yes, I think the breakage might have happened here: http://q-jenkins.ubuntu-ci:8080/view/cu2d/view/Head/view/WebCreds/job/cu2d-webcred-head-1.1prepare-uoa-integration-tests/364/console
[17:15] <sil2100> plars: seems to be some random failure?
[17:15] <sil2100> plars: it was the previous run of webcreds, automatic build I guess
[17:16] <kenvandine> oh, i killed a webcred build over the weekend, it was never going to finish because of libaccounts-glib dep wait
[17:16] <kenvandine> maybe that caused it?
[17:18] <kenvandine> the job had been running for 2 days, waiting for webcred build job to finish, which was in dep wait in the ppa
[17:18] <plars> sil2100, kenvandine, fginther: I can restart http://q-jenkins.ubuntu-ci:8080/job/cu2d-webcred-head/ now and we'll see if it's better then?
[17:19] <kenvandine> worth a shot i guess
[17:19] <sil2100> plars: sure
[17:21] <plars> sil2100: I've not restarted one of these, which packages or other parameters should I feed it? or just leave all of them blank?
[17:21] <sil2100> plars: you can leave all blank, then it will do a standard run with rebuilding what needs to be rebuilded
[17:21] <plars> ack
[17:23] <plars> sil2100, kenvandine: looks better so far :)
[17:23] <kenvandine> good
[17:23] <plars> http://q-jenkins.ubuntu-ci:8080/job/cu2d-webcred-head-1.0prepare/
[17:23] <kenvandine> plars, stx
[17:23] <popey> sil2100: / didrocks sorry I missed the meeting, I have a personal appt at this time.
[17:23] <popey> didrocks: was there an update to the online accounts plugin ask?
[17:24] <didrocks> popey: no worry, as there is no promotion under way ;)
[17:24] <popey> ok
[17:24] <didrocks> popey: the evernote one, but not anything else
[17:25] <popey> didrocks: any idea when we might see it landing?
[17:25] <popey> or at least reviewed ☻
[17:26] <didrocks> popey: evernote? soon soon, when sil2100 will succeed in running prepared (see the failure discussion above ^)
[17:26] <popey> ah
[17:26] <didrocks> if everything goes smootly before sil2100's EOD I guess ;)
[17:26]  * popey scrolls
[17:26] <sil2100> popey: yes, we wait for the webcred stack to finish
[17:26] <popey> k
[17:26] <sil2100> Once it finishes, I'll just press the send button and violla
[17:27] <didrocks> "voilà" ;)
[17:27] <sil2100> didrocks: just in case - is the whitelist updated? ;)
[17:27] <sil2100> didrocks: ;p
[17:27] <didrocks> sil2100: doing for safety ;)
[17:28] <didrocks> (done)
=== gatox_lunch is now known as gatox
[17:52] <sergiusens> didrocks, notes app should be in any minute; tested on mako and generic (emu)
[18:06] <sil2100> didrocks, kenvandine, popey: evernote published, it's in the queue now
[18:06] <didrocks> tranks guys :)
[18:07] <sil2100> See you tomorrow :) !
[18:11] <popey> \o/
[18:29] <kenvandine> fginther, your upstart-app-launch rebuild failed, same failure
[18:29] <dobey> robru: hi
[18:29] <robru> dobey, hello
[18:31] <dobey> robru: i see your name in the PoCs column for unity-scope-click/ubuntu-purchase-service landing. just wondering what sort of time frame we should expect to see it done, as we have "frozen" trunk right now to avoid piling more stuff on, and will need to un-freeze it when the current stuff is landed
[18:32] <robru> dobey, i was just going to start on that right now
[18:32] <dobey> robru: great. i'm just curious about timeframe, because i have no idea how long these landing requests typically take. i guess this one will take a bit longer than normal as it's quite a bit of fixes, and a new package
[18:33] <robru> dobey, yeah, could be a couple of hours. first i have to kick builds, then then I have to run a bunch of manual tests, then I have to poke at it. probably 4 hours tops, depending on how long the builds & the tests take to run.
[18:34] <dobey> robru: ah ok. fwiw, the latest versions seem to be built in the daily-build ppa already, from saturday
[18:34] <robru> dobey, oh, no new commits since saturday? so that speeds things up then ;-)
[18:35] <dobey> robru: nope, last commit was on friday
[18:36] <robru> dobey, confirmed. ok, i just have to run the tests then. shouldn't be more than an hour or two
[18:36] <dobey> robru: great! please ping me when it's done. and thanks. :)
[18:37] <robru> dobey, ok, no worries
=== fginther changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: fginther | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: -
[18:40] <fginther> kenvandine, looking
[18:40] <kenvandine> fginther, thx
[18:42] <fginther> kenvandine, argh! there were two dh packages that machine was missing, I only installed one of them.
[18:42] <kenvandine> :)
[18:43] <fginther> kenvandine, I'll restart it in a moment
[18:59] <sergiusens> kenvandine or robru care to check https://code.launchpad.net/~sergiusens/usensord/package_prio/+merge/201492 ?
[19:00] <robru> sergiusens, approved
[19:03] <sergiusens> robru, ty
[19:05] <kenvandine> fginther, now the i386 build failed :)
[19:12] <robru> kenvandine, cyphermox: does anybody know what the 4 regressions for unity8 are? I'm currently trying to test purchase-service and seeing http://paste.ubuntu.com/6746370/ but not sure if those are the known regressions or if purchase-service broke those
[19:12] <fginther> kenvandine, same problem, different host. sorry
[19:12] <fginther> I assumed that host was already updated
[19:13] <cyphermox> robru: http://ci.ubuntu.com/smokeng/trusty/touch/mako/125:20140113:20140107.1/6032/unity8-autopilot/ ?
[19:13] <cyphermox> but that would only be two of them I guess
[19:13] <cyphermox> robru: check the reports in general
[19:14] <robru> cyphermox, hm, yeah, that's two of them...
[19:15] <davmor2> rsalveti: https://bugs.launchpad.net/unity8/+bug/1268693 that's the info gathered so far
[19:16] <ubot5> Ubuntu bug 1268693 in Unity 8 "Possible bug in mir/memory on maguro" [Undecided,New]
[19:16] <davmor2> rsalveti: don't know if there is anything of any use
[19:55] <robru> dobey, ok, published unity-scope-click and ubuntu-purchase-service. feel free to land merges in trunk now.
[19:56] <dobey> robru: great. thanks!
[19:56] <robru> dobey, y
[19:56] <robru> dobey, you're welcome
[19:59] <rsalveti> davmor2: cool, let me check
[20:37] <rsalveti> davmor2: just updated the bug, do you have the unity8 log as well?
[20:37] <rsalveti> only interesting line is coming from the app:  QUbuntu: Could not create application instance
[21:34] <sergiusens> fginther, thomi if I want something in trusty's autopilot; what branch should I create the MR against?
[21:34] <fginther> kenvandine, finally! http://s-jenkins.ubuntu-ci:8080/job/upstart-app-launch-trusty-i386-ci/64/
[21:36] <fginther> sergiusens, lp:autopilot unless thomi disagrees with me
[21:36] <sergiusens> ack
[21:42] <sergiusens> fginther, hmmm, lp:autopilot looks nothing like what is release :-/
[21:44] <fginther> sergiusens, I think it's been a while since lp:autopilot has made it into distro
[21:45] <sergiusens> fginther, I sort of need something in sooner than later so I'll do a debian patch if it comes to it
[21:45] <fginther> but I don't know if that explains what you are seeing
[21:45] <sergiusens> fginther, meh, not even :-)
[21:46] <sergiusens> fginther, yeah, it's been a while, so debian patch it is ;-)
[21:46] <thomi> sergiusens: lp:autopilot, and we'll stabilise it into the release series for the next + 1 release
[21:46] <sergiusens> thomi, what is the plan for stuff we need now?
[21:47] <sergiusens> as in distro
[21:47] <thomi> sergiusens: OTP, one second
[21:57] <kenvandine> fginther, yay... thanks!
[22:36] <thomi> sergiusens: hey, I'm back
[22:36] <thomi> sergiusens: what's the patch?
[22:39] <sergiusens> thomi, http://paste.ubuntu.com/6747393/
[22:40] <sergiusens> thomi, or just the patch http://paste.ubuntu.com/6747399/
[22:41] <thomi> sergiusens: is this really urgent enough to justify shipping a distro patch?
[22:41] <sergiusens> thomi, I can do that or disable all the gallery and media player tests
[22:42] <thomi> sergiusens: OK, so if you ship it as a distro patch, please also make a MP against lp:autopilot with tests to cover the new functionality
[22:42] <thomi> that way we can roll it into a regular release
[22:42] <thomi> as it is, it looks like this code is untested
[22:42] <sergiusens> thomi, hmm, but the code has changed so much
[22:42] <sergiusens> thomi, I'll log a bug perhaps
[22:43] <thomi> sergiusens: what I'm saying is: please dont' ship a distro patch without at least making an attempt to upstream the change
[22:43] <thomi> the new code is actually easier to modify, not harder
[22:43] <thomi> plus, it has 100% unit test coverage
[22:43] <thomi> so your change should be easy to add :)
[22:44] <sergiusens> thomi, please release it into the distro then
[22:45] <thomi> sergiusens: believe me, we're trying
[22:45] <thomi> sergiusens: we're in the middle of the release process right now. If you have concerns, you need to speak to jfunk about it :)
[22:48] <sergiusens> thomi, you should release more often; this just complicates things; I'll talk to jfunk
[22:49] <thomi> sergiusens: dude, we're trying... really. If it were up to me I'd release once a week at least
[23:02] <sergiusens> thomi, so what is blocking you now?
[23:08] <thomi> sergiusens: you really need to talk to jfunk about that - he's managing the release process. AIUI, we're waiting on some response from the release team, but I may be wrong about that
=== fginther changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: -
[23:47] <cjwatson> thomi: not seeing anything relevant either on the release list or in our subscribed bug list
[23:48] <thomi> there's a release list? anyway, as I said earlier, jfunk said he was sending the email - maybe he doesnt know about the list either?
[23:48] <thomi> or maybe he just hasn't sent it yet? I'm guessing now
[23:48] <cjwatson> https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
[23:49] <thomi> cjwatson: that's not a replacement for the spreadsheet though, I take it?
[23:49] <cjwatson> this is a six-year-old list, it can't possibly be a replacement for something less than a year old
[23:49] <cjwatson> it's not touch-specific
[23:49] <cjwatson> just as the release team (without qualifiers) is not touch-specific
[23:50] <cjwatson> if you mean the touch landing team then that's something different ...
[23:50] <cjwatson> (or whatever the latest name for it is, but at any rate we should take care to avoid name collisions with something that already exists)