[16:27] <roaksoax> rvba: howdy!! I was wondering if you guys already have a ETA for the multiple environments storage fix? I just wanna have on idea on when we can do the SRU
[16:29] <rvba> roaksoax: Hi.  We just finished sketching out a plan for this.  Now we're working on the code. End of next week seems like a reasonable ETA. <- allenap, what do you say?
[16:30] <allenap> rvba: Yeah, that sounds about right.
[16:32] <roaksoax> rvba: awesome, thanks!
[17:04] <roaksoax> rvba: so what are the reasons why trunk maas can't run in precise?
[17:04] <roaksoax> other than dependencies
[17:06] <rvba> roaksoax: there is only the dependencies issue AFAIK
[17:06] <rvba> The only reason we have 2 branches (trunk and 1.2) is because we added 2 new features in trunk that were considered "too much" to be SRUed.
[17:07] <roaksoax> rvba: which ones are those?
[17:07] <rvba> roaksoax: offline operation and user commissioning scripts
[17:08] <roaksoax> rvba: ack! thanks
[17:08] <rvba> np
[17:09] <roaksoax> rvba: and kernel params too
[17:10] <roaksoax> rvba: what are the dependencies that differ?
[17:11] <rvba> roaksoax: I think kernel params have been backported to 1.2
[17:11] <roaksoax> rvba: nah
[17:13] <roaksoax> rvba: what are the dependencies that trunk has that make it impossible to work on precise?
[17:14] <rvba> roaksoax: I don't know offhand
[17:14] <rvba> roaksoax: 1.2 and trunk are so similar that I even wonder how the dependencies differ…
[17:17] <roaksoax> rvba:  iirc bigjools did ssy that trunk wont eork in prrcise
[18:02] <roaksoax> rvba: ok this it what i'll do
[18:02] <roaksoax> rvba: i'll upload 1.2 to raring, then to precise-proposed and quantal-proposed before FF
[18:02] <roaksoax> rvba: once I do that, I'll upload trunk to raring
[18:02] <roaksoax> before FF
[18:02] <roaksoax> rvba: but then when your fix is really, will upload it to -precise-proposed and quantal-proposed
[18:03] <rvba> roaksoax: do we really have to upload now?
[18:04] <roaksoax> rvba: i', not really concerned with raring TBH
[18:04] <roaksoax> rvba: and the upload to -proposed will sit there for a while
[18:04] <roaksoax> rvba: and once it gets approved it will be there for SRU verification
[18:05] <roaksoax> so it is not really gonna be released right after upload
[18:05] <roaksoax> rvba: as far as raring, nobody will be upgrading current environments right? since raring is still in development
[18:05] <rvba> roaksoax: if yes, then I suggest you don't upload the last version.  But instead r 1438 in trunk and r 1361 in 1.2
[18:06] <roaksoax> rvba: the plan is to get multiple environments fix rather than a new feature for the SRU
[18:06] <rvba> Because we've changed the way the file storage works and that change will only be properly complete when the fix we're working on will be released.
[18:06] <roaksoax> smoser: ^^
[18:07] <roaksoax> rvba: right but upgrading from 1363 to 136X should be fixed right?
[18:08] <rvba> roaksoax: what do you mean?
[18:08] <smoser> ugh.
[18:08] <smoser> roaksoax, unless daviey or sru team told you otherwise, just upload something to raring. its a pre-relesae snapshot. thats fine. it has bugs.
[18:08] <roaksoax> rvba: so if I release 1363 (1.2) to raring, then I release 136X (which contains your fix), then upgrading will fix the problem right?
[18:09] <smoser> whether or not we wait for the multiple-environment bug fix or not to upload to -proposed (quantal and precise) is un-related.
[18:09] <roaksoax> smoser: yeah that's what I'm planning to do
[18:09] <smoser> and i'd just upload a trunk snapshot to raring.
[18:09] <smoser> somethign that passed basic test.
[18:10] <roaksoax> smoser: i'll upload lp:maas/1.2 to raring, then to {precise,quantal}-proposed, and since it is gonna sit there for a while we'll wait for the bug to be released in trunk and update -proposed . But in the meantime, upload a trunk snapshot
[18:10] <roaksoax> do I make sense?
[18:10] <rvba> roaksoax: it will, but it you use 1363 you might encounter serious bugs.
[18:11] <smoser> why do you bother uploading maas/1.2 to raring ?
[18:11] <roaksoax> rvba: yes which is why it will be sitting in -proposed :)
[18:11] <smoser> ugh.
[18:11] <smoser> don't upload something to -proposed that we're not happy to release.
[18:12] <rvba> +1
[18:12] <rvba> The bug we're fixing is really ugly.
[18:12] <smoser> but i'm do not think that this maas multi-user thing is significant.
[18:12] <smoser> no one is using that
[18:12] <smoser> and its not a regression
[18:12] <rvba> It is.
[18:12] <smoser> it is a regression from something in ubuntu ?
[18:13] <roaksoax> ok then I'll upload trunk to -raring
[18:13] <smoser> rvba, ?
[18:13] <roaksoax> trunk will be released as 1.3
[18:13] <roaksoax> and SRU will have 1.2~bzr136X, which is nowhere in the archives
[18:14] <smoser> wait to see if rvba says this is a regression, but otherwise, i'm fine with that.
[18:14] <rvba> smoser: this is really tricky tbh.
[18:14]  * rvba thinks
[18:14] <smoser> "tricky" isn't answering the question :)
[18:14] <roaksoax> if it gets rejected by the SRU team because we are backpoirting a new upstream which is nowhere in ubuntu, then we are screwed :)
[18:14] <rvba> smoser: That's why I need to think :)
[18:14] <smoser> roaksoax, honestly, if it does, then that is silly.
[18:15] <smoser> because, as you've suggested, there is a very stupid workaround for that process requirement.
[18:15] <roaksoax> smoser: well I came across a situation like that long time ago and was told "you can only backport something that is in the archive"
[18:15] <smoser> roaksoax, then if you want to, upload a 1.2 to raring. i'm fine with that too.
[18:16] <smoser> but i tihnk that it wont be a sticking issue on sru
[18:16] <rvba> smoser: I think it's a regression.  If you have 2 users, you'll definitely see a regression.
[18:16] <smoser> remember, you're also not allowed to entirely new packages
[18:16] <smoser> or features.
[18:16] <smoser> rvba, you see that if you have 2 users on current quantal mas and you upgrade to 1.2 ?
[18:17] <smoser> is that what your'e saying ?
[18:17] <rvba> Yes.
[18:17] <smoser> if only we had unit tests
[18:17] <smoser> then we'd neer see bugs like this.
[18:17] <smoser> roaksoax, i say hold off on it then. i dont want to upload a regression to sru.
[18:18] <roaksoax> smoser: right but this time we got a TB exeption
[18:18] <smoser> but imo upload whatever you want to raring. we're already in major exception mode.
[18:18] <smoser> this little thing is a very minor exception.
[18:18] <rvba> smoser: this problem is not because of the lack of unit tests.  It;s because we had to rush something to meet a crazy deadline at some point, and now we're paying the price for it.
[18:18] <roaksoax> i will just upload trunk to raring
[18:19] <smoser> and doing the dance to avoid that exception will cause you to make another exception (FFE)
[18:19] <roaksoax> i'll continue as suggested, upload trunk (1.3) to raring, and SRU 1.2
[18:20] <smoser> roaksoax, right. but dont bother sruing without the fix for bug 11239986
[18:20] <smoser> 1123986
[18:20] <roaksoax> smoser: i won't SRU until it gets fixed
[18:20] <rvba> roaksoax: why don't you upload 1.2 revision 1361 and trunk revision 1438 ?
[18:21] <roaksoax> rvba: 1263 has IPMI fixes
[18:21] <roaksoax> err 1363
[18:21] <rvba> The problem is only that right now, we're half way through fixing the multiple env bug.
[18:22] <roaksoax> and I need to make available those IPMI fixes to raring too
[18:22] <roaksoax> but we need tests for them
[18:22] <roaksoax> so that will take me couple days maybe
[18:22] <roaksoax> and then i'll upload trunk to raring
[18:22] <roaksoax> wait for your fix
[18:23] <roaksoax> and upload 1.2 tyo -proposed
[18:23] <rvba> Ok, I take it no one is using raring in prod now so it does not really matter.
[18:24] <roaksoax> exactly
[18:24] <rvba> Just don't upload the current tip of trunk or 1.2 before next week's fix to an important place :)
[18:25] <roaksoax> raring is fine to have bugs so raring is not really a concern
[18:25] <rvba> Right.
[18:26] <rvba> So you'll wait until next week for the other uploads right?
[18:30] <roaksoax> rvba: yeah
[18:30] <rvba> roaksoax: ok, thanks.
[18:30] <roaksoax> rvba: no worries :) just fix that bug i'll take care of the rest :)
[18:30] <rvba> roaksoax: we're on it, you can trust me.
[18:32] <roaksoax> i do :)
[18:32] <roaksoax> you've never disappointed so I'm really not concerned :)
[18:34] <rvba> Good :)