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