/srv/irclogs.ubuntu.com/2011/04/12/#ubuntu-meeting.txt

=== Ursinha-afk is now known as Ursinha
SergioMenesesbuenas...02:49
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
=== doko_ is now known as doko
=== yofel_ is now known as yofel
=== Claudinux_ is now known as Claudinux
=== thermi is now known as Thermi
=== Sarvatt is now known as Sarvatt|2
=== Sarvatt_ is now known as Sarvatt
zulhi16:53
RoAkSoAxo/16:53
kirklando/16:58
smb /o\16:59
JFo /o/ \o\ /o/16:59
JFo:)16:59
smbJFo, Just in case this will be the server team meeting I believe. ;)17:00
JFoyeah17:00
* JFo lurks17:00
SpamapSRoAkSoAx: do not suffer the lazy and tardy.. I suggest that you begin! :)17:01
RoAkSoAx#startmeeting17:01
MootBotMeeting started at 11:01. The chair is RoAkSoAx.17:01
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]17:01
jamespageo/17:01
RoAkSoAx[TOPIC] Review ACTION points from previous meeting17:02
MootBotNew Topic:  Review ACTION points from previous meeting17:02
RoAkSoAxFirst of:17:02
RoAkSoAxDaviey to submit UDS-O topic for translations and docs17:02
RoAkSoAxwhat's the status17:02
RoAkSoAxDaviey: ?17:02
DavieyI've spoken to David P about it... he seems excited, and will certianlly attend17:02
DavieySo it's essentially done, it will happen - just not drafted17:03
DavieyMark as done17:03
Davieysorry for being brief - otp.17:03
RoAkSoAxalrighty!17:03
RoAkSoAxlet's move on then17:03
RoAkSoAxjamespage to helpout with verification of euca-dhcp bug17:03
zuli think thats been done17:04
robbiewo.17:04
robbiewo/17:04
jamespageVerified - yes - by me - no - required - no - so mark as DONE17:04
robbiewsorry..late17:04
RoAkSoAxjamespage: awesome!17:04
RoAkSoAxjamespage to discover process/location for fixing ubuntu server documentation17:04
jamespageOK - so docs here are now up-to-date : https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#Documentor resources17:04
jamespageWe where not far off TBH - loads of stuff on the documentation team wiki pages as well17:05
smosero/'17:05
RoAkSoAxany further action to be taken?17:05
jamespagenot from my perspective17:06
RoAkSoAxalrighty then. Let's move on then17:06
RoAkSoAx[TOPIC] Natty Development17:06
MootBotNew Topic:  Natty Development17:06
RoAkSoAxrobbiew: ^^17:06
robbiewso...I'd like to propose Daviey take this section over ;)17:07
SpamapShttp://people.canonical.com/~platform/workitems/natty/canonical-server.html17:07
MootBotLINK received:  http://people.canonical.com/~platform/workitems/natty/canonical-server.html17:07
SpamapSstill a few items remaining17:07
* Daviey is off the phone17:07
robbiewI can cut and paste links...as above ;)17:07
RoAkSoAxDaviey: go for it :)17:07
robbiewin terms of development...I'm more interested in Bugs now anyway17:07
DavieySorry, somewhat unprepared.17:08
robbiewany remaining work items should be universe related or non-code17:08
robbiewDaviey: no worries...I'm always that way :P17:08
DavieyI think mainly, people need to make sure the blueprints are updated.17:08
SpamapSDaviey: do we still have an auto-generated report from the server-n* tags ?17:08
DavieySpamapS, Yes17:09
DavieyThat is what i've mainly been tracking this week tbh.. it's more uselful at this stage for specific bug tracking,than WI.17:09
DavieyIMO17:09
SpamapSawesome. ;)17:09
Davieyhttps://bugs.launchpad.net/ubuntu/+bugs?field.tag=server-nrs17:09
SpamapSWI is almost done anyway, so yeah bugs are where its at. :)17:09
RoAkSoAxawesome then17:10
RoAkSoAxanyone has anything to add?17:10
SpamapSShould show milestoned bugs as purple on the WI tracker. ;)17:10
DavieyRoAkSoAx, ok to move on...17:11
RoAkSoAxalright, I guess there's nothing else,17:11
RoAkSoAx[TOPIC] Ubuntu Server Team Events17:11
Davieybut make sure WI's are up to date :)17:11
MootBotNew Topic:  Ubuntu Server Team Events17:11
RoAkSoAxany event coming up?17:11
SpamapSTOMORROW I'm speaking at the MySQL User's Conference about Drizzle in Natty17:11
RoAkSoAxSpamapS: \o/17:11
SpamapSSanta Clara, CA .. be there, or be square.17:11
zulill be there...just not this week17:12
jamespageGood luck SpamapS - is it due to be video cast?17:12
SpamapSjamespage: not likely, its a massive event.17:12
DavieySpamapS, Looking forward to reading your blog post about it :)17:12
SpamapSjamespage: and it will be at 3:15pm UTC -0700 ..17:12
RoAkSoAxmaybe would be a good thing to video tape all the events/talks on which ubuntu server member participate, to share them with the community17:12
DavieyRoAkSoAx, Thanks for volunteering to be the team camera man.17:13
RoAkSoAxDaviey: no worries if I can travel lol :)17:13
zulyou stole my soull..17:13
RoAkSoAxanyway, let's move on17:13
RoAkSoAx[TOPIC] Weekly Updates & Questions for the QA Team (hggdh)17:13
MootBotNew Topic:  Weekly Updates & Questions for the QA Team (hggdh)17:13
RoAkSoAxhggdh: you are up17:13
Davieyhey hggdh o/17:13
hggdhyo17:13
* SpamapS just finished downloading the latest iso's17:13
hggdhgoing thru euca now17:14
SpamapSits ISO testing time yes?17:14
DavieySpamapS, cautionary17:14
hggdhinitial ISO tests via jenkins are all done, with success except for ec2 -- will discuss with jamespage17:14
DavieyThe current posted ISO will be deprecated later today, so not too much investment... But sniffing is useful.17:15
jamespagehggdh - they have not been run yet.17:15
hggdhjamespage: they _were_ running this morning (mine morning)17:15
Davieyhggdh / jamespage: Is there any news on email failures of failed jenkins tests?17:15
hggdhDaviey: no, yet to look at it17:15
Davieyok, thanks17:16
jamespagehggdh: that was some adhoc testing to determine whether we where still getting network failures on startup - looked OK17:16
hggdhI think it would be more productive to discuss jenkins usage on UDS -- where we would like it to go17:16
hggdhinstead of just ad-hoc additions17:16
hggdhjamespage: roger, thanks17:16
jamespagehggdh: agree17:17
RoAkSoAxalright, I guess a session will be held at UDS17:17
RoAkSoAxanything else to add?17:17
hggdh..17:17
hggdh:-)17:17
RoAkSoAxmoving one then17:17
RoAkSoAx[TOPIC] Weekly Updates & Questions for the Kernel Team (smb)17:17
MootBotNew Topic:  Weekly Updates & Questions for the Kernel Team (smb)17:17
Davieyone mo17:17
smbevening17:18
Davieyhggdh, are you going to drive a blueprint on that?17:18
Daviey(sorry smb)17:18
* smb waits17:18
hggdhDaviey: I can. Under QA, you mind?17:18
Davieyhggdh, that sounds like a good place!17:19
DavieyThanks17:19
Davieysmb, Hi o/17:19
smbI am good to go? :)17:19
RoAkSoAxsmb: the floor is yours now :)17:19
smbOk, I try to leave as qquickly17:19
smbBasically main task is still going on lucid-ec2 patches17:20
smbnow at 16 new and 35 changed of the 147 to go17:20
Davieysmb, Do you have the bug numbers handy?17:20
smbThat has not yet a bug number17:20
DavieyAre they tagged?17:20
smbI will need to create one of "bring our patchset up to date with the one we were taking our  patches from"17:21
zulsmb: may god have mercy on your soul17:21
Davieysmb, sounds good to me... We appreciate this :)17:21
smbI had been booting somewhere in the middle on ec2 and it surprisingly worked17:22
SpamapSHave we run automated ec2 tests since bug 731878 was fixed?17:22
ubottuLaunchpad bug 731878 in Linux "shutdown(2) behavior changed in kernel" [Medium,Confirmed] https://launchpad.net/bugs/73187817:22
smbBut ok, atm it does not compile again17:22
smbSpamapS, Hm, I don't know17:23
jamespageSpamapS: yes - I was unable to run in all regions but I did not see any instances failing to startup - http://jenkins.qa.ubuntu-uk.org/view/natty-ec2/job/natty_server_ec2_adhoc/5/17:23
smbIn the spare time I only looked over bug 75125317:24
ubottuLaunchpad bug 751253 in linux (Ubuntu) "Many interrupts and slow disk I/O on Lucid xen guest" [Undecided,New] https://launchpad.net/bugs/75125317:24
smbBut really that sounds a bit like maybe xen version or actually a lot of traffic as that machine had 500GB going out in 5 days17:25
SpamapSjamespage: will keep fingers crossed that it was indeed this kernel bug. :)17:25
jamespageSpamapS: me to!17:25
RoAkSoAxalright, anything else to add?17:26
smbI would not have more if there are no questions17:26
RoAkSoAxanyone with questions?17:26
RoAkSoAxI guess not. Moving on:17:26
RoAkSoAx[TOPIC] Weekly Updates & Questions for the Documentation Team (sommer)17:26
MootBotNew Topic:  Weekly Updates & Questions for the Documentation Team (sommer)17:26
RoAkSoAxI believe it is time for us to consider removing this topic from the agenda17:27
SpamapSWell17:27
RoAkSoAxSpamapS: have you been in recent contact with sommer?17:27
SpamapSI'd like to see the contact person changed.17:27
RoAkSoAxSpamapS: sounds like you are volunteering :)17:27
SpamapSRoAkSoAx: no, but I haven't tried much. Adam has moved on for now. :-/17:27
SpamapSI would love to do it, but I doubt I'd be very effective at actually getting things done.17:28
RoAkSoAxI guess that for now we can remove the item from the agenda till we have a replacement to cover this topic17:28
RoAkSoAxany objections?17:28
RoAkSoAxI'll take that as a yes to remove it from the agenda then17:29
RoAkSoAxok, so moving on17:29
RoAkSoAx[TOPIC] Weekly Updates & Questions from the Ubuntu Community17:30
MootBotNew Topic:  Weekly Updates & Questions from the Ubuntu Community17:30
kim0Howdy everyone o/ .. Got a quick announcement to make17:30
kim0I will be running a weekly community IRC meeting for the Ensemble team. This will be run in #ubuntu-cloud starting tomorrow at 6pm-UTC, it will be merged with the older community meeting. Everyone attending this meeting is a good candidate to attend tomorrow's17:30
kim0That meeting will provide a high level overview of development in the Ensemble world since last meeting/week17:30
kim0I'm writing an announcement on http://cloud.ubuntu.com/ right now, which I'll mirror on planet, and everyone is encouraged to spread/tweet...etc17:30
kim0That's all for me17:30
RoAkSoAxawesome!17:31
RoAkSoAxanyone else with questions/suggestions/or anything?17:31
RoAkSoAxlet's move on then17:31
RoAkSoAx[TOPIC] Open Discussion17:31
MootBotNew Topic:  Open Discussion17:31
SpamapSOh hah I missed that.17:31
kirklandRoAkSoAx: anyone else throwing a Natty Release Party?17:32
* SpamapS would like to thank Time Warner's extreme lag for that wrong/window17:32
kim0hehe17:32
RoAkSoAxkirkland: throught FL yes... miami... uhmmm it is hard enough to get an Ubuntu hour17:32
kirklandRoAkSoAx: here's one we're having in Austin: http://blog.dustinkirkland.com/2011/04/austins-natty-release-party.html17:32
zulill be doing my customary release party thing...sleeping17:33
RoAkSoAxkirkland: unfortunately, not even my Univerty's LUG is that much involved in events17:33
kirklandzul: heh17:33
kirklandzul: don't get toooo excited now17:33
RoAkSoAxok so anyone else attending/organizing a release party?17:34
kirklandRoAkSoAx: apparently not :-)17:34
RoAkSoAxor is everybody gonna party with zul in their dreams?17:34
zulthat sounds bad17:35
RoAkSoAxheheh17:35
* RoAkSoAx blames it to the language barrier17:35
RoAkSoAx:P17:35
kirklandwell, I'm going to drink a beer in celebration of Natty, and one more in looking forward to Oneiric17:35
RoAkSoAxkirkland: +1. I might do it alone but at least I'll have a beer17:35
RoAkSoAxanyways.17:35
RoAkSoAxlet's end the meeting17:35
RoAkSoAx[TOPIC] Announce next meeting date and time Tuesday, April 19th 2011 16:00 UTC17:36
MootBotNew Topic:  Announce next meeting date and time Tuesday, April 19th 2011 16:00 UTC17:36
RoAkSoAxsee you all next week same time/place17:36
RoAkSoAx#endmeeting17:36
kirkland\o17:36
MootBotMeeting finished at 11:36.17:36
JFoo/17:59
apwo/17:59
hertono/17:59
sconklin\o17:59
jjohansen\o17:59
sforsheeo/17:59
bjf#startmeeting18:00
MootBotMeeting started at 12:00. The chair is bjf.18:00
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]18:00
bjf##18:00
bjf## This is the Ubuntu Kernel Team weekly status meeting.18:00
bjf##18:00
bjf[LINK] https://wiki.ubuntu.com/KernelTeam/Meeting18:00
bjf[LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Natty18:00
MootBotLINK received:  https://wiki.ubuntu.com/KernelTeam/Meeting18:00
MootBotLINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Natty18:00
bjf# Meeting Etiquette18:00
bjf#18:00
bjf# NOTE: '..' indicates that you are finished with your input.18:00
bjf#       'o/' indicates you have something you'd like to add (wait until you are recognized)18:00
bjf#18:00
bjf[TOPIC] Release Metrics (JFo)18:00
MootBotNew Topic:  Release Metrics (JFo)18:00
JFoRelease Meeting Bugs (10 bugs, 8 Blueprints)18:00
JFo==== Beta 2 Milestoned Bugs (43 across all packages (down 21)) ====18:00
JFo * 4 linux kernel bugs (up 2)18:00
JFo * 0 linux-ti-omap4 bugs (no change)18:00
JFo * 0 linux-meta-ti-omap4 bug (no change)18:00
JFo==== Release Targeted Bugs (244 across all packages (down 28)) ====18:00
JFo * 32 linux kernel bugs (up 5)18:00
JFo * 1 linux-ti-omap4 bugs (changed to package omap4)18:00
JFo * 0 linux-meta-ti-omap4 bug (changed to package omap4)18:00
JFo==== Milestoned Features ====18:00
JFo * 6 blueprints (Including HWE Blueprints)18:00
JFo==== Maverick Updates Bugs ====18:00
JFo * 6 Linux Bugs (no change)18:01
JFo==== Lucid Updates Bugs ====18:01
JFochanged to only reflect linux package bugs18:01
JFo * 15 Linux Bugs (no change)18:01
JFo==== Bugs with Patches Attached:86 (down 1) ====18:01
JFo * [[https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.has_patch=on | Bugs with Patches]]18:01
JFo * [[http://qa.ubuntu.com/reports/ogasawara/csv-stats/bugs-with-patches/linux/ | Breakdown by status]]18:01
JFo..18:01
bjf[TOPIC] Blueprints: Natty Bug Handling (JFo)18:01
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-bug-handling18:01
MootBotNew Topic:  Blueprints: Natty Bug Handling (JFo)18:01
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-bug-handling18:01
JFo* nothing to report today18:01
JFo..18:01
bjf[TOPIC] Status: General Natty (apw / ogasawara)18:01
MootBotNew Topic:  Status: General Natty (apw / ogasawara)18:01
apwo/18:01
apwThe natty kernel is now at v2.6.38-8.42 (v2.6.38.2 based) [thank you Leann], following the upstream stable branch.  Following some uploads for compiler changes we are now frozen for the natty-beta-2 release.  We are also going to be in Kernel Freeze by the itime we come out of beta freeze.  This implies that from now on we will only take high priority bugs before release.  It also implies we now need full SRU acks for all changes.18:01
apw..18:01
bjf[TOPIC] Status: Stable Kernel Team (sconklin / bjf)18:02
MootBotNew Topic:  Status: Stable Kernel Team (sconklin / bjf)18:02
sconklin||18:02
sconklin|| All kernels in this cycle are awaiting signoff by certification and QA, and are then ready to be published.18:02
sconklin||18:02
sconklin|| The Lucid kernel was respun after verification to add a single patch that resolves a regression. This single18:02
sconklin|| patch was cherry-picked from the set of upstream stable patches which are currently queued for the next18:02
sconklin|| Lucid update, and therefore does not requrie verification.18:02
sconklin||18:02
sconklin..18:02
bjf[TOPIC] Security & bugfix kernels - Maverick/Lucid/Karmic/Hardy/Dapper (sconklin / bjf)18:02
MootBotNew Topic:  Security & bugfix kernels - Maverick/Lucid/Karmic/Hardy/Dapper (sconklin / bjf)18:02
sconklin|| Package                                    || Upd/Sec              || Proposed             ||  TiP || Verified ||18:02
sconklin||                                            ||                      ||                      ||      ||          ||18:02
sconklin|| dapper   linux-source-2.6.15               || 2.6.15-57.94         || 2.6.15-57.95         ||    0 ||        0 ||18:02
sconklin||                                            ||                      ||                      ||      ||          ||18:02
sconklin|| karmic   linux-ec2                         || 2.6.31-308.28        || 2.6.31-308.29        ||    1 ||        1 ||18:02
sconklin|| ---      linux                             || 2.6.31-23.74         || 2.6.31-23.75         ||    1 ||        1 ||18:02
sconklin||                                            ||                      ||                      ||      ||          ||18:02
sconklin|| lucid    linux-ec2                         || 2.6.32-314.27        || 2.6.32-315.28        ||    5 ||        5 ||18:02
sconklin|| ---      linux-ports-meta                  || 2.6.32.30.23         || 2.6.32.31.23         ||    0 ||        0 ||18:02
sconklin|| ---      linux-meta-lts-backport-maverick  || 2.6.35.25.36         || 2.6.35.28.37         ||    0 ||        0 ||18:02
sconklin|| ---      linux-lts-backport-maverick       || 2.6.35-25.44~lucid1  || 2.6.35-28.50~lucid1  ||   13 ||       13 ||18:02
sconklin|| ---      linux-backports-modules-2.6.32    || 2.6.32-30.29         || 2.6.32-31.31         ||    0 ||        0 ||18:02
sconklin|| ---      linux-firmware                    || 1.34.4               || 1.34.7               ||    1 ||        1 ||18:03
sconklin|| ---      linux                             || 2.6.32-30.59         || 2.6.32-31.61         ||    5 ||        5 ||18:03
sconklin|| ---      linux-meta                        || 2.6.32.30.36         || 2.6.32.31.37         ||    0 ||        0 ||18:03
sconklin|| ---      linux-meta-ec2                    || 2.6.32.314.15        || 2.6.32.315.16        ||    0 ||        0 ||18:03
sconklin||                                            ||                      ||                      ||      ||          ||18:03
sconklin|| maverick linux-backports-modules-2.6.35    || 2.6.35-28.19         || 2.6.35-28.20         ||    0 ||        0 ||18:03
sconklin|| ---      linux-ti-omap4                    || 2.6.35-903.21        || 2.6.35-903.22        ||    1 ||        1 ||18:03
sconklin|| ---      linux-firmware                    || 1.38.5               || 1.38.6               ||    2 ||        1 ||18:03
sconklin|| ---      linux                             || 2.6.35-28.49         || 2.6.35-28.50         ||    7 ||        7 ||18:03
sconklin||                                            ||                      ||                      ||      ||          ||18:03
sconklin..18:03
bjf[TOPIC] Incoming Bugs: Regressions (JFo)18:03
MootBotNew Topic:  Incoming Bugs: Regressions (JFo)18:03
JFoIncoming Bugs18:03
JFo 655 Natty Bugs (up 81)18:03
JFo 1255 Maverick Bugs (up 3)18:03
JFo 1064 Lucid Bugs (up 3)18:03
JFoCurrent regression stats (broken down by release):18:03
JFo==== regression-update ====18:03
JFo  * 47 maverick bugs (up 1)18:03
JFo  * 77 lucid bugs (no change)18:03
JFo  * 6 karmic bugs (no change)18:03
JFo  * 0 hardy bugs (no change)18:03
JFo==== regression-release ====18:03
JFo  * 335 natty bugs (up 48)18:03
JFo  * 249 maverick bugs (up 3)18:03
JFo  * 223 lucid bugs (up 1)18:03
JFo  * 38 karmic bugs (no change)18:03
JFo  * 2 hardy bugs (no change)18:04
JFo==== regression-proposed ====18:04
JFo  * 17 natty bugs (up 2)18:04
JFo  * 1 maverick bugs (up 1)18:04
JFo  * 0 lucid bugs (no change)18:04
JFo  * 0 karmic bug (no change)18:04
JFo..18:04
bjf[TOPIC] Incoming Bugs: Bug day report (JFo)18:04
MootBotNew Topic:  Incoming Bugs: Bug day report (JFo)18:04
JFonothing to report18:04
JFo..18:04
bjf[TOPIC] Triage Status (JFo)18:04
MootBotNew Topic:  Triage Status (JFo)18:04
JFonothing to report18:04
JFo..18:04
bjf[TOPIC] Open Discussion or Questions: Raise your hand to be recognized (o/)18:04
MootBotNew Topic:  Open Discussion or Questions: Raise your hand to be recognized (o/)18:04
bjfthanks everyone18:04
bjf#endmeeting18:04
MootBotMeeting finished at 12:04.18:04
JFothanks bjf that is a record18:04
JFo:)18:04
sconklina new record!18:05
sconklinThanks18:05
apwspeedy indeed :)18:05
ppisatia new record :)18:05
=== Mkaysi is now known as MKAYSI
smbThere has been a meeting? :-P18:07
=== dholbach_ is now known as dholbach
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
=== MKAYSI is now known as Mkaysi
=== Ursinha is now known as Ursinha-afk
* wendar waves19:07
wendarWho's here for the ARB meeting?19:07
* stgraber waves19:07
* wendar pinging others19:08
wendarwe may not have enough people for voting, but we can at least do status updates19:10
wendar#startmeeting19:12
wendar[TOPIC] Review action items19:12
wendar[LINK] http://wiki.ubuntu.com/AppReviewBoard/Agenda19:12
MootBotMeeting started at 13:12. The chair is wendar.19:12
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]19:12
MootBotNew Topic:  Review action items19:12
MootBotLINK received:  http://wiki.ubuntu.com/AppReviewBoard/Agenda19:12
wendarstgraber: I don't know of any progress on the actions from last meeting, do you?19:14
stgrabernope, there wasn't anything on the mailing-list, so I guess it's safe to carry them all over to the next meeting19:14
wendarcarried over19:15
wendar[TOPIC] Proposal Review19:15
MootBotNew Topic:  Proposal Review19:15
wendar[LINK] https://bugs.edge.launchpad.net/ubuntu-app-review-board19:15
MootBotLINK received:  https://bugs.edge.launchpad.net/ubuntu-app-review-board19:15
wendarno changes on existing proposals19:16
stgraberhmm, not sure why suspended-sentence is still listed on the wiki, it's been on extras.u.c for a while now19:16
stgraberpytask still hasn't moved a bit (waiting for new version)19:17
wendargood point, I'll remove suspended-sentence19:17
wendarthere's an update proposal for the news app19:17
stgraberwe have a new version of news that needs reviewing. I can take it as I did a quick review of the previous version19:17
stgraberdo, you were faster :)19:17
stgraber*doh19:18
wendar:)19:18
stgraberI assigned the news update to me and will review the change soon. Shouldn't be too hard at least, the packaging should already be good19:19
stgraberso this one should be ready for approval + upload at our next meeting19:20
wendarexcellent19:21
wendarI think that's it for proposal review19:21
wendar[TOPIC] Chair for next meeting19:22
MootBotNew Topic:  Chair for next meeting19:22
wendarstrgraber: do you want to chair next time?19:22
wendaror, should we skip it, since it's release week?19:22
stgraberI'd be tempted to skip it as it's release week and we'll all be busy with other stuff19:22
stgraberwould be cool if we could have quorum for our next meeting19:23
wendarour next meeting after release week is at UDS19:24
stgraberI'm probably going to ask for other ARB members to go vote for the news update directly in the bug report once it's in good shape19:24
wendarso, hopefully we can do it face-to-face19:24
wendarthat's a good idea19:24
wendarwe should talk at UDS about making ticket sign-offs the primary voting strategy19:25
stgraberyep, meeting at UDS would be good. Not sure how much of ARB is going to be in Budapest, but probably more than we currently have in this meeting anyway :)19:25
wendaryou, me, mvo, and hopefully ajmitch19:25
wendarIIRC, fagan couldn't make it19:25
wendarI'll update the agenda to note UDS as the next meeting19:26
wendarsounds like a wrap19:28
stgraberindeed19:28
wendar#endmeeting19:28
MootBotMeeting finished at 13:28.19:28
wendarthanks, stgraber!19:28
stgraberthanks19:29
mvowendar: I'm happy to attend a meeting at UDS20:11
mvo(I know I'm later :/)20:11
=== Thermi is now known as thermi
=== dutchie_ is now known as dutchie
=== Ursinha-afk is now known as Ursinha
=== emma_ is now known as em
=== dutchie_ is now known as dutchie

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!