[12:19] <nats> hello
[12:23] <pochu> hi nats
[12:23] <nats> how are you?
[12:24] <pochu> nats: fine :)
[12:24] <pochu> and you?
[12:24] <nats> fine
[12:24] <nats> thx
[12:25] <pochu> :)
[12:25] <pochu> ubuntu rocks!
[12:25] <pochu> @schedule madrid
[12:25] <Ubugtu> Schedule for Europe/Madrid: Current meeting: Ubuntu Development Team | 05 Feb 21:00: Mozilla Team | 07 Feb 13:00: Edubuntu | 08 Feb 17:00: Ubuntu Development Team | 13 Feb 17:00: Forum Council | 13 Feb 21:00: Technical Board
[12:26] <nats> what's it?
[01:06] <Seveas> @topic
[11:05] <pitti> seb128, Mithrandir: so, as I said I did syncs, removals, and SRU now; SRU takes quite a lot of time, but I'm fine with doing some source NEW as well
[11:06] <Mithrandir> should we discuss the agenda first? :-)
[11:06] <pitti> ok :)
[11:06] <pitti> - assign responsibilities
[11:06] <Mithrandir> * archive team days
[11:06] <pitti> - work out archive days schedule
[11:06] <pitti> ?
[11:06] <Mithrandir> yeah, I guess those are the important ones.
[11:07] <pitti> so what do we need to do: syncs, source new, binary new, removals, cruft, sru, promotions/demotions
[11:07] <pitti> anything else?
[11:08] <pitti> oh, backports
[11:08] <Mithrandir> yeah, and freeze exceptions at one point, but I'll in general be happy to take those.
[11:08] <seb128> stable updates?
[11:09] <Mithrandir> == sru
[11:09] <seb128> ah, right
[11:09] <pitti> Mithrandir: right, freeze exceptions are RMish
[11:09] <Mithrandir> ok, so what would people like to do?
[11:10] <seb128> I'm happy to do syncs, binary new, removals
[11:10] <pitti> <- sru, syncs, removals, help with source new (but this should be done by several people)
[11:10] <cjwatson> also you *will* be asked to investigate weird shit :-)
[11:10] <cjwatson> I can keep on doing cruft and the odd bit of other stuff
[11:11] <pitti> seb128: you often need main promotion as well, I guess?
[11:11] <cjwatson> and backports I suppose, though I'd like not to be the only one
[11:11] <seb128> pitti: right
[11:12] <seb128> I'm happy to help on backports as well
[11:12] <cjwatson> is somebody taking minutes?
[11:12] <Mithrandir> I am
[11:12] <pitti> cjwatson: I'll send a report
[11:12] <pitti> oh, ok
[11:13] <pitti> Mithrandir: so you do freeze exceptions and also source new?
[11:13] <Mithrandir> yes, I'm trying to write up a matrix here to see if there's stuff uncovered
[11:14] <pitti> oh, and I guess I'm the natural choice for langpack processing :)
[11:14] <cjwatson> every so often somebody has to clean up crap on drescher because soyuz doesn't clean up the queues automatically yet. I'm happy to do that
[11:14] <Mithrandir> nobody's grabbed promotions/demotions, but that's not really much work.
[11:14] <pitti> right, I'm happy to demote stuff :)
[11:15] <Mithrandir> syncs - pitti, seb
[11:15] <Mithrandir> source new - pitti
[11:15] <Mithrandir> binary new - seb,
[11:15] <Mithrandir> removals - pitti, seb
[11:15] <Mithrandir> sru - pitti
[11:15] <Mithrandir> promotions/demotions -
[11:15] <Mithrandir> langpacks - pitti, cjwatson
[11:15] <Mithrandir> backports - seb, cjwatson
[11:15] <Mithrandir> freeze stuff - tfheen
[11:15] <Mithrandir> cleanup - cjwatson
[11:15] <Mithrandir> is what I have so far.
[11:15] <Mithrandir> (I haven't put me in yet)
[11:15] <Mithrandir> I'll do NEW.
[11:16] <pitti> Mithrandir: put me in for promotions/demotions (and maybe seb, too)
[11:17] <Mithrandir> I can help out with SRUs too
[11:17] <Mithrandir> that leaves us with two people for all of it, except freeze stuff and cleanup.
[11:18] <pitti> ok, but cleanup doesn't need to be done that often, or does it?
[11:18] <pitti> this stuff is mainly useful for ensuring that the archive stuff keeps being done even if someone is on vac
[11:19] <Mithrandir> yup
[11:19] <pitti> Mithrandir: I'm not sure whether it's a good idea to have several people for freeze exceptions -- how much work is it?
[11:19] <Mithrandir> not much work, and it ties very closely in with doing the release management.
[11:20] <Mithrandir> so I'm happy to have that alone.  It shouldn't matter except when we're in freeze mode, in which case the RM should be around anyway. :-)
[11:20] <pitti> ok, are we settled with that?
[11:20] <Mithrandir> (and if I happen to go sick or something, somebody else will have to do the RM-ing and can then just pick up the exceptions too)
[11:20] <Mithrandir> yes, I am.
[11:21] <Mithrandir> seb128,cjwatson : are you two too happy?
[11:21] <pitti> what's the matrix now?
[11:21] <seb128> yep
[11:21] <Mithrandir> syncs - pitti, seb
[11:21] <Mithrandir> source new - pitti, tfheen
[11:21] <Mithrandir> binary new - seb, tfheen
[11:21] <Mithrandir> removals - pitti, seb
[11:21] <Mithrandir> sru - pitti, tfheen
[11:21] <Mithrandir> promotions/demotions - pitti, seb
[11:21] <Mithrandir> langpacks - pitti, cjwatson
[11:21] <Mithrandir> backports - seb, cjwatson
[11:21] <Mithrandir> freeze stuff - tfheen
[11:21] <Mithrandir> cleanup - cjwatson
[11:21] <pitti> great
[11:22] <pitti> and of those, syncs, new, sru, backports, and pro/demotions need to be done regularly, AFAICS
[11:22] <seb128> looks fine to me
[11:22] <pitti> so, personally I find it better and more efficient to batch things, so if it's my archive day, I'd do all of my tasks in one piece
[11:22] <Mithrandir> ok, so on to archive days.
[11:23] <pitti> so is everyone fine with doing archive maintenance on mon, wed, and fri?
[11:23] <pitti> (since the regular tasks cover three archive maintainers)
[11:23] <pitti> then we shouldn't crash into each other and spread out processing across the week
[11:23] <Mithrandir> experience from this cycle so far points to me having problems doing archive days in release weeks, but other weeks are very archive-heavy.
[11:24] <pitti> Mithrandir: I think this isn't set in stone, we can always ask someone else to cover
[11:24] <Mithrandir> well, true
[11:24] <pitti> but if it's X's archive day, it should be his responsibility to get it done or delegated?
[11:24] <Mithrandir> and if I grabbed monday, it should be fine anyway.
[11:25] <pitti> seb128: so maybe wed for you and fri for me?
[11:25] <seb128> wed works fine for me
[11:25] <Mithrandir> ok, let's make it so.
[11:25] <pitti> ok, then I'll do the pending stuff today
[11:25] <pitti> while seb is still collecting logins and team memberships
[11:25] <Mithrandir> pitti: please don't do binary NEW until herd 3 is out.
[11:25] <Mithrandir> or at least not for stuff in main.
[11:25] <pitti> Mithrandir: right, just syncs and sru today
[11:26] <Mithrandir> yeah, that's fine.
[11:26] <pitti> the syncs will just land in unapproved, right?
[11:26] <Mithrandir> hmm
[11:26] <pitti> I won't touch promotion/demotion either
[11:26] <Mithrandir> I'm unsure, actually.
[11:26] <Mithrandir> so try not to sync stuff in main today?
[11:26] <pitti> Mithrandir: ok, let's defer syncs as well
[11:26] <Mithrandir> thanks.
[11:26] <pitti> right, so no main processing today to be on the safe side
[11:27] <pitti> alright, that covers it for my part
[11:27] <pitti> everyone happy?
[11:27] <seb128> yep
[11:27] <pitti> great
[11:27] <pitti> seb128: what do you still need to actually get going?
[11:27] <seb128> what do you mean?
[11:27] <seb128> ah
[11:27] <pitti> cjwatson: could we do the langpack training sometimes soon? fixing dapper is kind of urgent
[11:28] <pitti> seb128: drescher login, sudo powers, team membership
[11:28] <Mithrandir> also, I'm happy to help out if there are questions or stuff which is unclear.
[11:28] <seb128> I need a drescher account with sudo powers on it
[11:28] <seb128> Colin sent a RT for it yesterday
[11:28] <pitti> seb128: ok; we have mon and friday covered, so that's ok for now, I think
[11:28] <seb128> right
[11:28] <cjwatson> Mithrandir: I'm happy
[11:29] <pitti> seb128: btw, I recently updated the ArchiveAdmin page with my new flush-syncs tool
[11:29] <Mithrandir> ok, coolie.
[11:29] <seb128> pitti: good ;)
[11:29] <Mithrandir> any other business?
[11:29] <seb128> nop
[11:29] <pitti> Mithrandir: just langpack training for me with Colin, nothing else
[11:29] <cjwatson> I think syncs go straight through, for the record
[11:29] <cjwatson> though I'd need to check whether the sync policy honours freeze status
[11:29] <pitti> ok, so better not touch main at all today
[11:30] <pitti> I'll just do SRUs today then
[11:30] <cjwatson> so, langpacks
[11:30] <cjwatson> obviously you first have to get them over to drescher somehow
[11:30] <pitti> Mithrandir: shall I mail ubuntu-devel-announce with the assignments and schedule or do you want to?
[11:30] <pitti> cjwatson: right, scp -r or rsync, I assume
[11:31] <Mithrandir> pitti: I can do it
[11:31] <cjwatson> then, as lp_queue, make a directory in ~lp_queue/manual-queue/incoming/
[11:31] <cjwatson> (like syncs, make it unique somehow - username + date is good)
[11:31] <cjwatson> dump all the uploads in there
[11:32] <cjwatson> then, still as lp_queue: NOMAILS=-M ~/manual-queue/process-incoming.sh
[11:32] <cjwatson> the NOMAILS bit is important obviously
[11:32] <cjwatson> it'll spam your terminal for about a week
[11:32] <cjwatson> then as lp_archive you'll need to approve them all in the relevant unapproved queue
[11:33] <cjwatson> q -s dapper-proposed -Q unapproved -M accept language-pack
[11:33] <cjwatson> again the -M is important
[11:33] <cjwatson> and again it'll spam your terminal for about a week
[11:34] <cjwatson> you can use DRYRUN='-N -K' (for process-incoming.sh) or -N (for queue) to dry-run if you like
[11:34] <cjwatson> though I only ever bother for a subset of language packs since there are so many
[11:34] <cjwatson> pitti: happy with that?
[11:34] <pitti> cjwatson: doesn't look too complicated
[11:35] <pitti> cjwatson: thank you; I'll try it out for dapper now and come back to you if there should be any trouble
[11:35] <cjwatson> yeah, it's simple enough, just hard to work out
[11:39] <pitti> 10:39:18 INFO    Announcing to dapper-changes@lists.ubuntu.com
[11:40] <pitti> cjwatson: ^ shall I take this seriously if I specified NOMALS=M?
[11:40] <pitti> NOMAILS=-M even
[11:41] <cjwatson> pitti: it should say something like "would be sending a mail"
[11:41] <cjwatson> the debug output is a bit dodgy in places
[11:41] <pitti> at least I didn't get any mails to -changes so far