QA/Meetings/20110627

From FedoraProject

Jump to: navigation, search

Contents

Attendees

People present (lines said):

  • jlaska (165)
  • rbergeron (40)
  • j_dulaney (34)
  • athmane (26)
  • vhumpa (25)
  • adamw (20)
  • tflink (18)
  • kparal (18)
  • Viking-Ice (11)
  • jskladan (10)
  • jsmith (6)
  • zodbot (5)
  • nirik (3)
  • brunowolff (1)

Unable to attend:

  1. Rhe (hopefully sleeping)
  2. Hongqing (hopefully sleeping)
  3. wutao85 (hopefully sleeping)

Agenda

Gnome Shell duplicate application names

  • On the terminal issue... xfce "terminal" is getting renamed to "xfce-terminal"
  • There are 3 s-c-* utilites that are *duplicate* to the gnome control panel applets and both show in overview when searched. Discussing the possibility of kicking them out of the menu using "NotShowIn=GNOME" in desktop file
  • Stay tuned to desktop@lists.fedoraproject.org for continued discussion
  • HELP: If you agree/disagree with kicking those 3 outta overview reply on the mailing list

AutoQA updates

  • We sorted out some issues caused by concurrent runs of the koji-bodhi watcher (refer to https://fedorahosted.org/autoqa/ticket/342)
  • tflink polished the autoqa notification routines so we don't 'spam' bodhi and developers with too much email
  • At tflink's suggestion, jlaska migrated our remaining production F13 test clients to F14
  • lmr announced autotest-0.13.0 last week (https://fedorahosted.org/pipermail/autoqa-devel/2011-June/002454.html) - packages available for test in autoqa -testing repo
  • j_dulaney asked for progress on yum bug resulting in missing depcheck results. tflink reported this will take more investigation to figure out. There is a change in 0.5.0 where the non-missing results are reported now (https://fedorahosted.org/autoqa/ticket/284 and https://fedorahosted.org/autoqa/ticket/325)
  • Team ready to package and deploy autoqa-0.5.0. Jlaska will update autoqa.spec in master, tflink will handle ChangeLog generation, and kparal will update the stable branch.
  • ACTION: kparal + jlaska to document autoqa release process on wiki

R3 - Retrospective recommendation review

Cloud SIG testing

  • To get cloud images up on Amazon, we have to have them go through the full Spins process. Which means we need signoff from QA, rel-eng, and Design.
  • Testers needed to help document test procedures (test cases / matrix) and run tests
  • Rbergeron will send mail to the cloud list (https://admin.fedoraproject.org/mailman/listinfo/cloud) to initiate the process, interested testers please follow-up on the list

Open Discussion - <your topic here>

Review Security Lab spin validation matrix

systemd updates from Viking-Ice

Critical Path Test Cases

Action Items

  1. kparal + jlaska to document autoqa release process on wiki
  2. jlaska - update ticket#154 with current critpath test coverage

IRC Log

jlaska #startmeeting Fedora QA meeting 15:00
zodbot Meeting started Mon Jun 27 15:00:03 2011 UTC. The chair is jlaska. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00
zodbot Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00
jlaska #meetingname fedora-qa 15:00
zodbot The meeting name has been set to 'fedora-qa' 15:00
jlaska #topic Roll Call 15:00
* jskladan tips his hat 15:00
athmane hello everyone 15:00
jlaska hello athmane + jskladan 15:00
* Viking-Ice joins inn 15:00
jlaska Hi Viking 15:01
* j_dulaney waves the chicken leg he is nomming on 15:01
* tflink is here 15:01
* jlaska greets j_dulaney and tflink 15:01
* brunowolff is here 15:01
* jsmith is here 15:01
jlaska hi bruno 15:01
jlaska woah, jsmith lurking! Everyone must be on their best behavior today 15:02
jlaska no cussing or spitting 15:02
jsmith Not lurking! 15:02
jsmith Actively participating! 15:02
j_dulaney Wow, our grand, exhalted leader graces us with his presence 15:02
jlaska lookout! 15:02
* jsmith isn't all that and a bag of chips 15:02
Viking-Ice fuck I mean frack :) 15:02
jlaska heh 15:02
jlaska who else we got ... 15:02
jlaska no robatino, adamw yet ... vhumpa is probably lurking 15:03
jlaska okay, let's get this party started ... 15:03
jlaska #link https://fedoraproject.org/wiki/QA/Meetings/20110627 15:03
vhumpa cheers! 15:04
jlaska I have a few additional side-topics that I need to add, but those will probably come up during open discussion 15:04
jlaska sweet, vhumpa's here ... so we can dive into hte first topic 15:04
vhumpa I idiot was stairing at wrong mailing list :) 15:04
j_dulaney Lulz 15:04
jlaska we have 1 item on the previous meeting follow-up list ... but it's related to the first topic ... so I'm moving straight to that 15:04
* kparal here 15:04
jlaska poof! Kamil lives! 15:04
jlaska #topic Gnome Shell duplicate application names 15:05
jlaska from last week I have ... 15:05
jlaska #info j_dulaney - will gather a full list of the application name collisions 15:05
jlaska does that still apply ... what's the latest on the dup application name front? 15:05
vhumpa Things are finally moving on this one 15:05
j_dulaney Indeed 15:05
* adamw tries to sneak in without the teacher noticing 15:05
* jlaska eyes yard stick 15:06
vhumpa On the terminal issue... xfce "terminal" is getting renamed to "xfce-terminal" 15:06
* j_dulaney notices and throws a spitball 15:06
* nirik notes this may be a while before it actually happens. 15:06
vhumpa With that should come change with the menu item too 15:06
vhumpa nirik: indeed, but at least it's happening 15:07
nirik yeah. 15:07
j_dulaney Maybe try to have it done by F16? 15:07
jlaska won't be a while just due to package rebuild ... or something else? 15:07
nirik the timeframe is really up to upstream. 15:07
vhumpa In addition to that, we have been discussing the issue of system-config-* utilities on the desktop list 15:07
jlaska #info On the terminal issue... xfce "terminal" is getting renamed to "xfce-terminal" 15:07
vhumpa There are 3 s-c-* utilites that are *duplicate* to the gnome control panel applets and both show in overview when searched 15:09
vhumpa date, printers and users 15:09
j_dulaney Plus the original Update(s) package issue that kicked things off 15:09
vhumpa j_dulaney: Indeed! 15:10
adamw upstream seems to accept renaming it in principle, but the bug's moving slow... 15:10
j_dulaney vhumpa: T'ealc much? 15:10
jlaska vhumpa: what's the plan for these ... make it more obvious that they are s-c-* utilities, rather than s/Printers/Printing/ 15:10
jlaska #info There are 3 s-c-* utilites that are *duplicate* to the gnome control panel applets and both show in overview when searched 15:10
vhumpa We were discussing the possibility of kicking them out of the menu 15:11
jlaska woah, fancy 15:11
vhumpa using "NotShowIn=GNOME" in desktop file 15:11
jlaska I see 15:11
vhumpa Thanks to the control panel applets, they are not really needed 15:11
jlaska do those utilities still have value over their gnome-shell control-center counterparts? 15:11
jlaska well, nm ... you answered that :) 15:12
adamw desktop team would also like not to install them by default at all, but that's slightly tricky due to installer / firstboot deps 15:12
vhumpa They need to stay in the system though - as they are needed by firstboot 15:12
jlaska ah, yeah yuck 15:13
vhumpa date and users in particular 15:13
vhumpa When it comes to non-gnome spins, they are needed for sure 15:13
jlaska is discussion happening on the desktop@ list for folks that want to get involved? 15:13
vhumpa jlaska: Yep! 15:13
j_dulaney Is there any way, on a Gnome install, to point Firstboot to the Gnome apps? 15:13
vhumpa I have also sent a summarizing to test list for people's feedback 15:14
adamw i think it may be a bit more complex than just 'pointing to' 15:14
jlaska #info Discussing the possibility of kicking them out of the menu using "NotShowIn=GNOME" in desktop file 15:14
vhumpa j_dulaney: nope 15:14
adamw but it would probably be possible to convert firstboot somehow, depends if anyone actually wants to do it though 15:14
j_dulaney vhumpa: Figured as much, but thought it couldn't hurt to ask 15:14
jlaska #info Stay tuned to desktop@lists.fedoraproject.org for continued discussion 15:14
vhumpa firstboot really seems to use parts of those and those specific 15:14
jlaska will have to see what comes out of this hub'and'spoke UI redesign for the installer/firstboot 15:15
jlaska but waaaay to early to see where that'll land (I think) 15:15
j_dulaney Indeed 15:15
jlaska thanks for the updates on this front ... anything else we need to cover/highlight in this meeting? 15:15
vhumpa Please, if you agree/disagree with kicking those 3 outta overview reply on the mailing list 15:16
adamw kicking them out *on kde and gnome*, they'd stay on other desktops - just to be clear 15:17
vhumpa On gnome really only 15:17
jlaska yes ... and this only removes them from menus as I understand 15:17
jlaska they may still be installed on the system and can be run by hand? 15:17
jlaska s/can/could/ 15:17
j_dulaney Indeed 15:18
vhumpa you can always run system-config-* manually 15:18
jlaska #help If you agree/disagree with kicking those 3 outta overview reply on the mailing list 15:18
jlaska okay, thanks all 15:18
jlaska if no objections, I'll move to the next topic 15:18
vhumpa Some people might still prefer the more time proven s-c-users e.g. 15:18
jlaska true 15:18
vhumpa jlaska: AutoQA! :-) 15:19
jlaska #topic AutoQA-0.5.0 ... coming to a deployment near you! 15:19
jlaska okay, who wants to give an update on the autoqa front? 15:19
* kparal looks around 15:19
jskladan we don't have much updates for the past week 15:19
jskladan the most important thing is that we're (IIRC) in the place where we can deploy 0.5 15:20
jskladan we sorted out some issues caused by concurrent runs of the koji-bodhi watcher 15:20
kparal #link https://fedorahosted.org/autoqa/ticket/342 15:20
jlaska #info We sorted out some issues caused by concurrent runs of the koji-bodhi watcher 15:21
jskladan and tflink polished the autoqa notification routines 15:21
j_dulaney tflink: How's that Yum bug going? 15:21
jskladan so we don't 'spam' bodhi and developers with too much email 15:21
j_dulaney Not really bug, but issue 15:21
tflink j_dulaney: yum bug? 15:21
jlaska #info tflink polished the autoqa notification routines so we don't 'spam' bodhi and developers with too much email 15:22
* j_dulaney is trying to recall preciesly what it was, something to do with the way Yum pulled stuff in and caused, I think it was depcheck, to sometimes not give resutls 15:22
jskladan Also the support for F13 in AutoQA was removed (we don't schedule any tests) 15:23
jlaska yay! 15:23
jskladan nothing else comes to my mind 15:23
kparal j_dulaney: there are multiple problems around this, not yet fully solved 15:23
jlaska #info At tflink's suggestion, I migrated our remaining production F13 test clients to F14 15:23
kparal jlaska: great 15:23
* jskladan looks around if someone else has anything to say 15:23
tflink j_dulaney: ah, that one. that's going to take a long time to figure out and has been put off for now. There is a change in 0.5.0 where the non-missing results are reported now 15:23
j_dulaney Righteo 15:24
jlaska #info lmr announced autotest-0.13.0 last week (https://fedorahosted.org/pipermail/autoqa-devel/2011-June/002454.html) - packages available for test in autoqa -testing repo 15:24
j_dulaney tflink or kparal, what's the ticket number? 15:24
tflink j_dulaney: for the missing builds issue? 15:25
j_dulaney tflink: Indeed 15:25
* tflink looking 15:25
tflink it's https://fedorahosted.org/autoqa/ticket/325 right now but we might want to check the wording of that ticket 15:26
jlaska #info j_dulaney asked for progress on yum bug resulting in missing depcheck results. tflink reported this will take more investigation to figure out. There is a change in 0.5.0 where the non-missing results are reported now (https://fedorahosted.org/autoqa/ticket/325) 15:26
tflink the original was https://fedorahosted.org/autoqa/ticket/284 15:26
j_dulaney Thanks much 15:26
tflink jlaska: that ticket was 284, 325 is for the eventual real fix 15:26
jlaska #undo 15:27
zodbot Removing item from minutes: <MeetBot.items.Info object at 0x1261ff0c> 15:27
jlaska #info j_dulaney asked for progress on yum bug resulting in missing depcheck results. tflink reported this will take more investigation to figure out. There is a change in 0.5.0 where the non-missing results are reported now (https://fedorahosted.org/autoqa/ticket/284 and https://fedorahosted.org/autoqa/ticket/325) 15:27
jlaska When do you want me to start packaging and deploying autoqa-0.5.0? 15:27
tflink jlaska: there are just a couple of doc issues that I need to finish up. I don't think anything else would be holding back release 15:28
kparal I believe so 15:28
* jskladan +1 15:28
jlaska can someone help me with the %changelog for autoqa-0.5.0-0.1.pre ? 15:28
kparal jlaska: I still didn't create the 'release process' wiki page 15:28
jlaska it needs some polish to sumarize the *big* changes 15:28
jlaska kparal: actually ... glad you mentioned that 15:28
kparal jlaska: I can do that tomorrow 15:29
jlaska I was going to document how I'm doing the builds now, and throw that on the wiki 15:29
jlaska kparal: I'll send what I come up with to autoqa-devel for review 15:29
jlaska #action kparal + jlaska to document autoqa release process on wiki 15:29
adamw jlaska: strictly the package changelog reflects changes in the package, not the app 15:29
jlaska adamw: ah ... good to know 15:30
jlaska well, I've seen it go eithe way 15:30
athmane the same happen to nitrate spec 15:30
jlaska we are upstream in this case ... so those traditional lines get a little fuzzy 15:30
jlaska perhaps what we need here is ... a CHANGELOG file provided by autoqa 15:30
jlaska where we can list the specific commits then? 15:31
jlaska and then I'll just do the less interesting packaging changes in %changelog? 15:31
kparal right, we can do that 15:31
kparal good idea 15:32
jlaska anyone know how to have that file generated automagically? 15:32
* jlaska has heard of some projects having that generated 15:32
kparal I would use that file for higher-overview changes 15:32
adamw jlaska: yes - changes in the code should be documented in a NEWS or ChangeLog in the codebase. 15:32
athmane git log :) 15:32
kparal not really a list of commits 15:32
adamw although some people skimp on that these days and just tell you to check out the git log. 15:32
kparal it's useless to duplicate git log imho 15:32
* jlaska looking at https://binarystatic.wordpress.com/2010/02/18/how-to-convert-git-log-to-changelog/ 15:32
tflink do we want to shoot for release today and deployment today or tomorrow then? 15:33
* jlaska votes for package today, deploy tomorrow 15:33
j_dulaney +1 15:33
kparal me+jskladan+vhumpa will leave after the meeting 15:33
kparal just to let you know 15:33
tflink OK, I can get a draft for the NEWS/CHANGELOG ready for review tomorrow 15:34
jlaska #link http://live.gnome.org/Git/ChangeLog 15:34
j_dulaney What all needs to be done to deploy? I have a fairly free afternoon. 15:34
jlaska tflink: okay thanks 15:34
* rbergeron lurks in 15:35
jlaska that's a good question ... 15:35
jlaska kparal: are you going to sync-up 'stable' with master now? 15:35
jlaska hi rbergeron 15:35
kparal jlaska: I'll tell you my preferred approach after the meeting :) 15:36
kparal just applied the same approach for my personal project 15:36
jlaska kparal: okay... I'll hold off on building until we've got that settled 15:36
tflink j_dulaney: I have a mental list but we can figure that out after the meeting :) 15:36
tflink the details, rather 15:36
j_dulaney tflink: Righteo 15:37
jlaska okay ... so sounds like figure out the git love needed, work up a Changelog file, tag build deploy tomorrow 15:37
* j_dulaney is thinking a Wiki page would be helpful, too 15:37
jlaska j_dulaney: yeah, kparal and I will get this started 15:37
jlaska so the process is at least documented 15:37
tflink jlaska: and prepare to spam people about spamming them less :) 15:37
jlaska yes, SPAM and blog :) 15:37
tflink i.e. announcements 15:37
jlaska "Prepare to *not* be spammed" 15:38
jlaska  :) 15:38
jlaska anything else on AutoQA? 15:38
kparal not from me 15:38
tflink nothing here either 15:39
jlaska okay, this will be an exciting week deploying ... nice work getting us here everyone 15:39
jlaska #topic R^3 - Retrospective recommendation review 15:39
jlaska #link https://fedoraproject.org/wiki/Fedora_15_QA_Retrospective#Recommendations 15:39
* adamw fails on feedback 15:40
jlaska The only thing I have to note here is that I'll be filing tickets this week to address recommendations 15:40
jlaska and then looking for volunteers to help work through the tickets, or find a good reason not to 15:40
jlaska hopefully the recommendations aren't surprises ... it's all from feedback you provided 15:40
* rbergeron nods 15:41
jlaska #info Tickets and hopefully an draft retrospective SOP coming this week 15:41
jlaska seems like rhe and adamw are already working some of the items addressed in the retrospective, so thanks to you both for getting started already 15:41
jlaska if no other comments/concerns/questions ... I'll move on 15:41
jlaska #topic Cloud SIG testing 15:42
jlaska And now for something completely different ... 15:43
jlaska I got a ping from rbergeron about a cloud testing opportunity in the coming weeks 15:43
j_dulaney My name is... Tim? 15:43
rbergeron Hi. :) 15:44
rbergeron So, in a nutshell: 15:44
adamw you're in a nutshell?! 15:44
adamw take that, lady gaga 15:44
rbergeron I AM 15:44
j_dulaney Must be a big nut 15:44
rbergeron Nutshells are the new eggshell 15:44
rbergeron To get cloud images up on Amazon, we have to have them go through the full Spins process. 15:44
rbergeron Which means we need signoff from QA, rel-eng, and Design. 15:44
jlaska #info To get cloud images up on Amazon, we have to have them go through the full Spins process. Which means we need signoff from QA, rel-eng, and Design. 15:45
rbergeron To get them through QA, we need to have a test plan, and test them. 15:45
rbergeron Or approved by QA. 15:45
rbergeron  ;) 15:45
jlaska well ... what I'd recommend is you need to have a documented test procedure at the least 15:45
rbergeron So what I'm essentially here to solicit is help with building a test plan, and then testing. :) 15:45
rbergeron Even guidance, really. 15:45
* tflink is interested 15:46
* j_dulaney is as well 15:46
j_dulaney SELF seems to have been a help here 15:46
jlaska as long as you have a test procedure documented ... and you follow that procedure when validating images, I think you've got enough to cover your bases 15:46
* athmane is interested, but i don't have amazon account :( 15:46
* rbergeron nods 15:46
jlaska athmane certainly has the experience writing test cases lately! :D 15:46
rbergeron The whole Amazon thing is a stickler, though I've got an email going to the Amazon liason dude. 15:46
rbergeron Who is new. 15:47
tflink are you looking at other cloud providers or just EC2? 15:47
* j_dulaney is wondering if it would be helpful to create a wiki to help with test plan creation? 15:47
rbergeron tflink: just EC2 atm. 15:47
jlaska j_dulaney: a wiki SOP that describes how to write test plans and cases? 15:47
j_dulaney jlaska: Indeed 15:47
jlaska j_dulaney: I think adamw might have what you need ... 15:47
* jlaska pulls up https://fedoraproject.org/wiki/Category:QA_SOPs 15:47
* j_dulaney doesn't need it, but it could be helpful for rbergeron 15:48
* rbergeron nods 15:48
jlaska #link https://fedoraproject.org/wiki/QA:SOP_test_case_creation 15:48
jlaska #link https://fedoraproject.org/wiki/QA:SOP_package_test_plan_creation 15:48
jlaska Those pages describe the process athmane has been following to create tests for specific packages ... which may be useful for the cloud SIG needs 15:48
* rbergeron nods 15:48
adamw let me know if it's full of crack 15:48
rbergeron i will do no such thing, i'll hoard it all for myself 15:48
rbergeron err 15:48
rbergeron I MEAN 15:48
jlaska hah 15:49
athmane jlaska: yep, and I love virt 15:49
j_dulaney rbergeron: Is there anything in the works to setup a general EC2 account for testing purposes like we discussed at SELF? 15:49
rbergeron Okay. So: I'll advertise this stuff on the Cloud SIG list. If anyone's interested in helping, we could *really* use the help, and it would go to something that lots of folks find useful. :) 15:49
rbergeron j_dulaney: Hoping Amazon Guy can help me out with that. 15:49
jlaska rbergeron: what's the time frame? 15:49
j_dulaney rbergeron: pop me an email with some details, and I'll give it a whack 15:50
rbergeron jlaska: Well, you know, hopefully before F16. We're already out a month. The sooner, the better, but I know that people are time-constrained. 15:50
rbergeron And our primary ec2 dude is on vaycay this week, as is dgilmore. 15:50
jlaska okay, for folks that are interested, stay tuned to cloud@lists.fedoraproject.org for an update from rbergeron? 15:50
rbergeron So it's not going to happen tomorrow. 15:51
rbergeron Yes, from me, unless I can convince someone else to take it on. :) 15:51
jlaska heh 15:51
jsmith rbergeron: dgilmore isn't on vacation, he's at a conference -- there *is* a difference :-p 15:51
rbergeron oh 15:51
rbergeron yeah, sorry. 15:51
jlaska heh 15:51
* rbergeron was shortening PTO for those not in the way of acronyms, but he's really OOO 15:51
j_dulaney The difference is in who pays for the booze 15:51
rbergeron lol 15:52
* athmane is thinking why not RH OpenShift too 15:52
rbergeron athmane: because that already includes the infrastructure. 15:53
rbergeron openshift is really for building apps that go on top of the infrastructure. 15:53
rbergeron Unless I missed something. ;) 15:53
jlaska anything else to discuss on this topic, or shall we take it to the cloud list? 15:53
athmane rbergeron: ok my mistake 15:53
rbergeron no worries. :) 15:54
rbergeron TO THE CLOUD 15:54
* jsmith facepalms 15:54
rbergeron https://admin.fedoraproject.org/mailman/listinfo/cloud 15:54
adamw to the cloud, on our magical unicorns! 15:54
* rbergeron slashes a Z with her sword in the air 15:55
rbergeron EOF. 15:55
jlaska #topic Open Discussion - <your topic here> 15:55
jlaska okay ... what'd I miss in the agenda? 15:55
athmane #link https://fedorahosted.org/fedora-qa/ticket/207 15:55
adamw yay athmane 15:56
Viking-Ice ok I got some systemd related topic 15:56
jlaska #topic Open Discussion - Review Security Lab spin validation matrix 15:56
jlaska Viking-Ice: okay, I'll come to that too 15:56
* jlaska agrees with adamw ... 15:56
jlaska nice work athmane! 15:57
athmane jlaska: thanks 15:57
jlaska is the intention for this matrix to be included in alongside the 'install', 'desktop', and 'base' test matrices when release validation happens? 15:57
athmane no, keeping it sparely is better imho 15:58
jlaska the reason I ask was more about the timing of when we need to run through this test matrix? 15:58
athmane I thins RC phase should be great 15:59
jlaska like if it would be included in the announcements that robatino and rhe send out ... or if you would be sending this out for testing at different times 15:59
athmane **think 15:59
athmane jlaska: different time 15:59
jlaska okay 15:59
athmane because we should focus on the base os first 16:00
jlaska right 16:00
athmane and sec spin seems a little inactive 16:00
adamw athmane: bear in mind that it's considered bad to make some major changes post-beta 16:00
adamw i tend to favour running tests as early and often as possible so you can fix things as early as possible 16:01
athmane adamw: desktop tests are covered with LXDE test matrix 16:01
jlaska yeah, we could certainly include this in each test run ... but not necesarily re-run *every* test each time 16:01
athmane the rest is security apps 16:01
jlaska perhaps just once per milestone (alpha, beta, final)? 16:01
adamw athmane: there are app-level changes in the category, like soname bumps for instance 16:02
jlaska #link s new changes. 16:02
jlaska #undo 16:03
zodbot Removing item from minutes: <MeetBot.items.Link object at 0x1e8e2aac> 16:03
jlaska #link https://fedorahosted.org/fedora-qa/ticket/207 16:03
athmane adamw: ?? 16:03
jlaska athmane: you might want to add a prefix or legend like we have in other matrices? 16:04
jlaska esp since this might go out to test audience who isn't already familiar with the other matrices we use 16:04
athmane jlaska: I'll check that 16:04
adamw athmane: it's not too important, wecan chat about it later 16:04
athmane ok 16:05
jlaska okay ... so thanks for getting this started athmane 16:05
jlaska we'll stay tuned to the ticket for additional review comments 16:05
jlaska #topic Open Discussion - systemd updates from Viking-Ice 16:05
jlaska Viking-Ice: take it away! 16:05
Viking-Ice Ok so it was decided ( originally for base ) that all services that ship on a livecd ( aiming at default here but cover all live iso if doable ) have to be converted to native systemd and correctly package before alpha or else they will block the release #link http://lists.fedoraproject.org/pipermail/devel/2011-June/152861.html 16:05
Viking-Ice A general tracker bug for systemd service convertion can be found here #link https://bugzilla.redhat.com/showdependencytree.cgi?id=713562&hide_resolved=1 16:06
* jlaska notes they are already proposed as blockers - https://fedoraproject.org/wiki/Current_Release_Blockers 16:06
Viking-Ice but a better tracker can be found here https://fedoraproject.org/wiki/User:Johannbg/Features/SysVtoSystemd 16:07
jlaska #link http://lists.fedoraproject.org/pipermail/devel/2011-June/152861.html 16:07
jlaska #info it was decided ( originally for base ) that all services that ship on a livecd ( aiming at default here but cover all live iso if doable ) have to be converted to native systemd and correctly package before alpha or else they will block the release 16:07
Viking-Ice There is also a bigger proposal here #https://fedorahosted.org/fesco/ticket/615 <-- 16:07
jlaska Viking-Ice: is this a feature of the F16 release? 16:07
j_dulaney jlaska: I think so 16:08
jlaska Viking-Ice: ah perfect, that's what I was missing 16:08
jlaska #link https://fedorahosted.org/fesco/ticket/615 16:08
Viking-Ice jlaska, sysvtosystemd is eys 16:08
jlaska #link https://fedoraproject.org/wiki/Features/SysVtoSystemd 16:08
jlaska cool, thanks for the update on this 16:09
jlaska Viking-Ice: anything else you wanted to call out on this ... or was this more a heads up? 16:10
Viking-Ice I think fesco/fpc has lined up provenpackagers to raid sloppy maintainers and finish packaging the needed service befor alpha since most of those service already have native systemd service files for them but just not package yet 16:10
Viking-Ice jlaska, this was more just of an heads up just pay attention to my wiki page it will be correctly update with progress 16:11
jlaska Viking-Ice: great, thanks for the heads up ... this will be a nice feature to have for F16 16:11
jlaska #topic Open Discussion - last call ... 16:11
jlaska okay, last call for topics 16:11
* jlaska sets #endmeeting fuse for 2 minutes 16:11
athmane critical path test cases 16:11
athmane lost ticket no 16:12
jlaska #topic Open Discussion - Critical Path Test Cases 16:12
jlaska #link https://fedorahosted.org/fedora-qa/ticket/154 16:12
jlaska woah, athmane you've been chipping away at these! 16:12
adamw yeah, nice stuff 16:12
athmane need to have how much pkg left 16:13
jlaska btw .. this ticket drives me nuts since it will never be completed 16:13
* jlaska used the dreaded _never_ word 16:13
athmane also jlaska 's script seems to compare pkg bin instead of srpm name 16:13
* Viking-Ice points out that Current_Release_Blockers page does contain service that are not relevant to the decide criteria like spamassasin smokeping etc 16:13
jlaska athmane: do you want me to do some queries to check for how many are remaning? 16:13
athmane jlaska: yes just update the ticket with the output 16:14
jlaska okay, I'll try to update that ... likely tomorrow 16:14
jlaska #action jlaska - update ticket#154 with current critpath test coverage 16:14
jlaska anything else to cover here? 16:15
athmane jlaska: I think it's good, thanks 16:15
jlaska thank you for contributing :) 16:15
jlaska #topic Open Discussion - last call 16:15
jlaska okay. ... setting the fuse for 2 minutes again 16:15
jlaska 1 minute until #endmeeting ... 16:16
jlaska Thanks everyone for your time ... apologies for running over today 16:17
jlaska I'll send minutes to the list shortly after the meeting 16:17
jlaska #endmeeting 16:17

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