15:00:06 #startmeeting 15:00:06 Meeting started Tue Nov 17 15:00:06 2009 UTC. The chair is tk009. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:06 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:22 BugZappers meeting starting 15:01:05 morning 15:01:12 hi 15:01:15 morning =) 15:01:23 hello johe 15:01:23 late afternoon :) 15:01:34 =) 15:01:35 i believe rjune sends his apologies 15:01:41 yes I saw that 15:01:43 something came up 15:01:47 ...and also, he can't come to the meeting 15:01:55 here, good morning 15:01:56 oh, i slay me. 15:01:59 hi tech33 15:02:14 * iarlyy here too 15:02:15 soeone needs their coffee? 15:02:56 anyone else in attendance that has yet to speak up 15:03:25 #topic - Semantics Change - Confirm and Implement 15:03:34 Welcome Fedora 12 Constatine... = ) 15:03:46 yes welcome =) 15:04:14 initial page was changed 15:04:15 = ) 15:04:36 tk009: indeed, f12 is split off and rawhide is back to being rawhide, so the semantics change should go into effect 15:04:45 * SMParrish late but here 15:04:48 SO we are offically now going to use keyword Triaged and no assigned for f13 bugs and beyond 15:04:59 to recap again - that means basically that instead of setting bugs to ASSIGNED after we triage them, we leave them at NEW and add the Triaged keyword 15:05:00 welcome SMParrish 15:05:06 for new bugs in Rawhide 15:05:16 new bugs in F12 and earlier stick with the older system 15:05:45 we should announce this on test-announce at least, possibly also devel-list i guess 15:06:00 anyone want to do that? should I? 15:06:18 is the greasemonkey script already updated with this change? ie one triage button for <= f12 and one for rawhide + 15:06:32 ooh. nice point. mcepl? 15:07:25 no takers on sending out that email? 15:07:29 a question.. when this bug will be assigned ... devel team decides from now? 15:07:44 yes iarlly 15:07:52 yep 15:07:58 that was the idea of the change 15:08:15 tk009: I can do the email, should be an easy one 15:08:21 great 15:08:32 thank you SMP =) 15:08:58 mcepl: can you update the greasemonkey script as suggested by smparrish? 15:10:44 #action smparrish to send out email notifying test-announce and devel-list about semantics change 15:10:55 oop, can you chair me tk009? or do that yourself? 15:11:03 #action SMParrish will email test-announce and -devel about the 'Triaged' change. 15:11:13 #chair adamw 15:11:13 Current chairs: adamw tk009 15:11:31 who wants an action item to follow up with mcepl when he's awake? :) 15:12:20 I will, if I'm allowed :) 15:12:28 yes you are =) 15:12:48 there is no allowed here 15:13:03 #action tech33 to follow up with mcepl about updating greasemonkey script for semantics change 15:13:28 that it for that one? 15:13:32 i think so 15:13:50 #topic - Bug Lifecycle - Wiki page and image changes 15:14:00 LINK: https://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow 15:14:41 we need the two changes adamw mentioned two weeks ago 15:14:50 i can change the text 15:15:20 I guess I get the iage 15:15:24 image* 15:15:46 alrighty 15:15:47 will you action both of those please adamw 15:15:54 you type faster hehe 15:16:00 well that and I am lazy =P 15:16:00 #action adamw to update bug workflow wiki page for semantics change 15:16:10 #action tk009 to update bug workflow wiki image for semantics change 15:16:37 #topic - Housekeeping - Discuss ongoing housekeeping 15:16:48 LINK: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora12 15:16:58 LINK: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/DayBeforeRelease 15:17:39 I am sure poelcat has the day before stuff covered 15:18:03 it was mostly confirmation and that we have with the GA today 15:18:34 LINK: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/FirstDayDevel 15:18:42 This is one we do 15:18:55 and one you mentioned in the QA eeting yesterday adamw 15:19:22 creating the blocker/tracker bugs for the next release 15:19:30 actually the f13 ones already exist 15:19:46 I created them last cycle 15:19:48 they get created two releases in advance, so what we need to do now is create the NEXT next blockers :) 15:19:50 f14 15:19:57 and can do it again 15:20:12 http://fedoraproject.org/wiki/BugZappers/HouseKeeping/Trackers 15:20:36 we also should close off the f12 blocker, and move up the subsidiary tracker bugs that are blocking it to f13 15:20:45 do you wanna take care of that tk009? 15:20:52 I can yes 15:20:57 thanks! 15:21:27 #action tk009 to do tracker bug housekeeping: create f14blocker and f14tracker, close off f12blocker and move subsidiary blockers up to f13 15:21:45 #topic - Open Floor 15:21:54 bring what you got 15:22:25 anyone need any help with any problems, or getting started bugzappin? 15:22:44 johe, ping 15:22:48 yes 15:22:50 hi 15:23:01 I guess first day here was yesterday right? 15:23:06 i think i could need a bit advice 15:23:23 now is the time... feel free to ask 15:23:32 well, i tried over the weekend, but it was very lonely on irc :-) 15:23:58 sorry :) 15:24:20 * mcepl was drawn away ... of course, Greasemonkey (and soon-to-come jetpack) script will be fixed 15:24:24 well, what to ask, first i read through the most of the stuff, but i have no good point/package to start, so any advice would be welcome 15:24:26 tk009: yes, I did the 'day before release' stuff 15:24:43 and the EOL warning will run tomorrow 15:24:47 poelcat =) I knew it was so 15:25:20 tk009: your reminders help too :) 15:25:34 johe I wanted to respond proper to your introduction email. 15:25:46 poelcat: I nag huh =) 15:27:19 we're getting jetpacks now?! awesome! 15:27:30 * mcepl scrolls through the backlog ... tk009 are going to make F14 blocker and F14 tracker??? Really? We know what will block F14? 15:27:35 johe: is there a component you feel most interested / expert in? 15:27:48 mcepl: that's the procedure, blockers and trackers get created two versions ahead of time. 15:27:56 mcepl: f13blocker has existed since f11 came out :) 15:28:01 OK, I ammissing on proceure 15:28:25 * mcepl is sick and his hands are sticky ... not good for keyboard 15:28:42 don't sneeze on the microphone :P 15:28:43 adamw, well wouldnt call me an expert on any, but i think most of the stuff could be handled 15:29:27 i work as an systemandministrator so any server related would be best i think 15:29:29 * mcepl will have questions in the end of the meeting on the design of scripts ... booking his time 15:30:24 we don't have any servers on the 'priority components' list 15:30:35 but you could certainly specialize in that area of triaging - it might be a nice thing to have covered 15:30:36 johe we can talk in bugzappers channel after the meeting if you have the time. 15:31:04 tk009, half an hour or so, before my girfriend comes home :-) 15:31:10 it looks like open apache bugs are not triaged, and there's 16 of them, which is a nice workable amount for a starting bugzapper - https://bugzilla.redhat.com/buglist.cgi?query_format=advanced&classification=Fedora&component=httpd&bug_status=NEW 15:31:22 then you could certainly look at the other typical server components 15:31:47 adamw, okay deal :-) 15:31:52 cool :) 15:32:22 I see upstart and SELinux available 15:32:31 note about IRC: i don't always follow everything said in -bugzappers, particularly on weekends, but if you poke me by name i'll get an alert to check on what you asked, and i will do it 15:32:31 mkinitrd 15:32:53 what a strange thing to say. 15:33:00 usually within a few minutes, but could be hours if i'm out or asleep 15:33:03 pjones: hum? 15:33:20 just "mkinitrd", without any adorning text or obvious context. 15:33:50 pjones: somebody's looking for components to start bug triaging 15:33:51 pjones: the context is "I see upstart and SELinux available" 15:34:01 he was adding mkinitrd to that list 15:34:14 mkinitrd isn't really worth triaging at this point, since it's deprecated. 15:34:15 mcepl: you're behind the technological curve, though 15:34:28 mkinitrd is the old bad thing now, dracut is the new hotness :) 15:34:57 adamw: well, I know I thought it is now aliased to dracut 15:35:04 no. 15:35:15 adamw: dracut is not on the list 15:35:28 mcepl: we should update it then 15:35:54 i think we did it based off a critical path snapshot from a few months back, we should probably check it every few months against a new critical path snapshot 15:35:57 OK 15:36:05 maybe stick that on the agenda for next week... 15:36:25 it will be done 15:36:49 Do we have anything else for today then? 15:37:01 * mcepl stands in the end of the line 15:37:23 * mcepl will have questions in the end of the meeting on the design of scripts ... booking his time 15:37:43 then its mcepls time now 15:37:49 break it down! 15:38:23 #chair mcepl 15:38:23 Current chairs: adamw mcepl tk009 15:38:37 do we really need two buttons ... couldn't the button say 15:38:37 if (version < 13 ) { makeAssigned } else { setTriagedKeyword } 15:38:38 ? 15:38:53 sounds good to me 15:39:06 can it also tell if the change it's about to be committed with would change the version and cope with that? 15:39:11 any other complaints, comments, whatever to the scripts? 15:39:24 (e.g. if you're changing an incorrectly-filed-on-rawhide bug to f12 and setting it as 'triaged' at the same time) 15:39:40 * adamw loves to come up with the awkward corner case :) 15:39:44 will think about this 15:39:49 yes we see that 15:39:53 hehe 15:39:53 sure, it should be possible 15:39:58 great 15:40:14 then that would definitely be better - simple interface wins, and it makes the semantic change almost transparent for people who use the script buttons 15:40:16 thanks! 15:40:39 some missing Buttons, something redundant, you hate blue? 15:41:06 I was always a fan of brown? =) 15:41:45 tk009: that would be launchpadBugTriage.user.js script I believe ;) 15:41:48 the scripts works like I expect, no complaints here 15:41:57 hehe 15:42:02 I can make colors configurable 15:42:38 no questions? 15:42:40 three 15:42:41 two 15:42:41 one 15:42:46 I think Iam done 15:43:14 okay then team, that is a wrap for today. Now go install f12 if you have not already 15:43:28 thank you all for coming 15:43:37 #endmeeting