[00:04] <joey> I just started the stub for 4.0.  https://dev.launchpad.net/VersionFourDotO
[00:04] <joey> for the community members on channel
[00:04] <wgrant> Aha.
[00:05] <wgrant> Is there a definite timeline for 3.0 yet?
[00:05] <joey> kfogel's been handling that (I've been off on temporary assignment)
[00:05] <joey> I saw something today in passing which seems to indicate it's gotten more solid but I haven't seen anything yet
[00:06] <joey> i.e. official
[00:06] <wgrant> OK.
[00:06] <joey> The anticipation is building though so I am hopeful we'll see something really soon now. ;-)
[00:07] <wgrant> I think the anticipation is more for the open-sourcing, though.
[00:07] <joey> and we're running out of July :-)
[00:07] <joey> yes! That's what I meant.
[00:07] <joey> anticipation and excitement
[00:08] <wgrant> July is no deadline any more...
[00:12] <wgrant> Why aren't the team hierarchies on the dev wiki consistent? Registry's test plans live at 'Registry Team/Registry Test Plans', Soyuz at 'Soyuz Test Plan', Code at 'Code Team Test Plans', Translations at 'Translations/Test Plans', and a few other variants for the other teams.
[00:21] <joey> wgrant: they were organic I think.  I certainly didn't prescribe what it should be, only that there should be test plans. :-)
[00:21] <joey> wgrant: I'll pass it on to matsubara and ursinha. Maybe they might tackle the inconsistency.
[00:22] <joey> ok, I'm going to bugger off for the day
[00:22] <joey> have a good one
[00:22] <wgrant> joey: Thanks.
[00:22] <wgrant> You too.
[13:21] <jtv> danilos: https://pastebin.canonical.com/19696/
[13:22] <danilos> jtv: thanks
[14:36] <danilos> jtv: I've emailed you the RT number if it doesn't get done by the end of the week
[14:36] <jtv> danilos: as if I don't have enough trouble getting losa attention :)
[14:37] <jtv> danilos: branch just landed on devel btw
[14:37] <danilos> jtv: to be honest, who doesn't? note that Tom is on vacation this week, which means it's harder for everyone, especially with him being the most responsive of them all IME :)
[14:37] <danilos> jtv: this is for bzr commit stuff, right?
[14:38] <jtv> danilos: I wouldn't know, I rarely start work that early.  :)
[14:38] <jtv> danilos: for that and other QA.
[14:38] <danilos> well, Tom would usually show up in a few hours from now
[14:39] <jtv> danilos: in my language you're saying "just before midnight."  :)
[14:40] <danilos> jtv: so, have you started on the bzr commit QA? (you'll get other QA done I know, but this one probably requires a few hours of constant presence with a LOSA which is harder for you)
[14:40] <jtv> danilos: just did a bit of preparation.  Not so sure it requires constant LOSA attention though.
[14:41] <danilos> jtv: I didn't say constant LOSA attention, I said it requires you being constantly there when you've got LOSA at hand
[14:41] <jtv> ah ok
[14:41] <jtv> well, I'm working on it.  :)
[14:43] <danilos> jtv: btw, has bug 383610 landed?
[14:43] <ubot3> Malone bug 383610 in rosetta "Message-sharing migration script allows duplicate TranslationMessages" [High,In progress] https://launchpad.net/bugs/383610
[14:44] <jtv> danilos: yes
[14:44] <danilos> jtv: I don't see it on devel
[14:45] <jtv> danilos: it's on db-devel, because it depends on a trigger change.
[14:45] <danilos> jtv: is it only on db-devel?
[14:45] <jtv> danilos: hang on, working with herb
[14:45] <danilos> jtv: ah, ok, so that's not something we can CP
[14:45] <danilos> jtv: sure, go on, that's fine, thanks
[14:46] <henninge> danilos, jtv: Does this mean that staging's data is as of Friday, 16:25 (whatever TZ)?
[14:46] <henninge> https://staging.launchpad.net/successful-updates.txt
[14:46] <danilos> henninge: most likely, yes
[14:47] <jtv> henninge: yes, it's Friday's data with later code.
[14:47] <henninge> thanks
[14:47] <danilos> henninge: there are enough import failures from before that date as well, so it shouldn't be hard to reproduce :)
[14:48] <henninge> Actually, there aren't that many in the logs on devpad, just 5.
[14:49] <danilos> henninge: right, it seems logrotate has messed it up, let me look up older ones and how they behave
[14:50] <henninge> danilos: don't bother right now
[14:50] <henninge> danilos: I will try the oldest I find there, first.
[20:57] <sinzui> flacoste: I am confused about where I need to /also/ merge the DateMarshaller fix. I think you said lp:lazr.restful and to update the changelog, but this tree does not have a changelog.
[21:58] <flacoste> sinzui: it should
[21:59] <flacoste> sinzui: in src/lazr/restful/CHANGES.txt i think
[22:00] <sinzui> flacoste: lp:lazr.restful AKA lp:~lazr-developers/lazr.restful/trunk does not. I can create one
[22:01] <flacoste> sinzui: hang on, i'm sure there is on
[22:01] <flacoste> sinzui: src/lazr/restful/NEWS.txt
[22:01] <sinzui> I see that
[22:01] <sinzui> thanks