[13:33] dholbach: your patch works nicely :) [13:33] davidcalle: shall I propose it or do you just want to push it to the branch? [13:33] we have both tested it, let's push it [13:34] great :) [13:34] hum.. are you pushing it now or shall I? [13:36] dholbach: pushed, was deleting my branch [13:36] * dholbach hugs davidcalle [13:37] http://pad.ubuntu.com/I52eWD9zXl [13:37] so now we need to see if we can fix the migrations, right? [13:39] dholbach, do we have migrations to fix? [13:39] davidcalle: on staging [13:39] or is all the stuff working on there now? [13:42] dholbach: staging has moved on to other testing (trunk). It appears that my plan of having staging to test "anything" won't work. The builds created there are used for prod... [13:43] dholbach: I discovered it this morning with IS [13:43] mh [13:43] dholbach: I've asked for help to create a local way to test the stack, in a rt [13:43] ok [13:43] that sounds like the reasonable way forward then [13:43] and we can default to landing stuff in trunk again [13:44] right? [13:44] yep [13:44] in that case we can also default to having code reviews again? [13:44] at least for stuff I propose I'd appreciate it [13:45] davidcalle: where are you having the conversation with IS? [13:46] I'm interested in that as well [13:47] dholbach: https://portal.admin.canonical.com/87084 [13:51] great, thanks [13:56] ah I thought that was about asking for instructions? [14:00] davidcalle: can you update that RT informing them of the new RT#87214 requesting an update to rev 156? [14:01] mhall119: ok === dholbach_ is now known as dholbach [15:21] mhall119, davidcalle: are we in the process of deploying something to prod? [15:22] I can't log in right now [15:23] dholbach: yes, and it broke [15:23] ok [15:39] davidcalle: I'm sure you have more important stuff to doright now, but here's https://code.launchpad.net/~dholbach/developer-ubuntu-com/1525202/+merge/280318 [15:47] dholbach: davidcalle: FYI, there was some problems with juju and/or prodstack, the devportal has been reverted to r145 until that's resolved, then they will try to update it to 156 again [15:48] crossing fingers then [15:48] mhall119: once all of this is landed, can we focus on the django / djangocms update or is there other stuff we still need to land after that? [15:50] dholbach: we're still waiting on fixed JS scope API docs I believe, which I'd like to publish as soon as we get them [15:50] everything else I think can wait on the django/cms upgrade [15:50] ok... I'd really like to get this done [15:51] I know [15:51] * mhall119 hugs dholbach [15:51] * dholbach hugs mhall119 back :) [15:52] I just know it won't happen if we don't all look at it together - let's just make sure we don't end up in a situation like this again - probably getting a local prod or staging-like environment for testing will make this all quicker ... and regularly checking if our components are getting a bit old :) [15:53] in any case: I didn't mean to criticise anyone [15:57] * davidcalle hugs dholbach [16:03] * dholbach hugs davidcalle back [16:13] dholbach: merged [16:14] davidcalle: https://code.launchpad.net/~dholbach/developer-ubuntu-com/update-pip-components/+merge/280323 [16:16] dholbach: I need to get my kids, but I'll have a look after [16:17] davidcalle: no worries [16:17] it's not that important :) [16:19] * davidcalle drives home, ttyl o/