From Fedora Project Wiki

< QA‎ | Meetings

(create initial page for 12-10 meeting)
 
(update page with the results of the meeting)
 
Line 1: Line 1:
= Attendees =
= Attendees =
* adamw (150)
* j_dulaney (36)
* tflink (22)
* Viking-Ice (21)
* kparal (20)
* jreznik (14)
* nirik (11)
* maxamillion (9)
* zodbot (8)
* jskladan (3)
* wwoods (3)
* satellit (3)
* BobJensen (3)
* pschindl (3)
* mjg59 (2)
* Martix (2)
* jsmith (2)
* mkrizek (1)


= Agenda =
= Agenda =
Line 9: Line 27:


== Previous meeting follow-up ==
== Previous meeting follow-up ==
* adamw to brief #fedora ops and fedora-user-list regulars on fedup
* ''adamw to brief #fedora ops and fedora-user-list regulars on fedup'' - he talked to some people, maybe not everyone
* adamw to put 'enterprise storage support in newui' on next week's agenda
* ''adamw to put 'enterprise storage support in newui' on next week's agenda'' - done!


== Fedora 18 Final status ==
== Fedora 18 Final status ==
* TC1 is out, where do we stand?
* Current schedule was: change deadlines 2012-12-11, go/no-go 2012-01-01, release date 2012-01-08
* fedup / SB plans?
* Final TC1 was available and viable for testing, but not Secure Boot-enabled
* Blocker list was substantial, at 28 proposed
* fedup GUI still was not available, some fixes for rough edges pending


== Enterprise storage support for F18 / F19 ==
== Enterprise storage support for F18 / F19 ==
* request from viking-ice last week, was discussed on anaconda list this week
* Enterprise/advanced storage types that require interaction to enable/use would not work via UI in in F18, but could be used via kickstart. UI is scheduled to re-appear in F19
* Agreed that this needed to be documented for final release


== Test case / criteria revision ==
== Test case / criteria revision ==
* Check in on recent criteria proposals and TC revision work
* RPM package error proposal positively received, should be put into practice
* Agreed that we couldn't agree on a kickstart criterion, instead agreed to handle kickstart bugs on a case-by-case basis for F18
* pschindl was working on test case adjustments for Final


== Open floor ==
== Open floor ==
N/A
== Action items ==
* tflink to clarify use of his fedup side repo
* viking-ice to let docs team know about advanced storage for release notes
* adamw to put packaging error criterion revision into production
* kparal to follow up on test@ discussion to explain the plan, and let anaconda team know


== IRC Log ==
== IRC Log ==
{|
|- id="t16:00:24"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | #startmeeting Fedora QA meeting
|| [[#t16:00:24|16:00]]
|- id="t16:00:24"
! style="background-color: #42427e" | zodbot
| style="color: #42427e" | Meeting started Mon Dec 10 16:00:24 2012 UTC.  The chair is adamw. Information about MeetBot at http://wiki.debian.org/MeetBot.
|| [[#t16:00:24|16:00]]
|- id="t16:00:24"
! style="background-color: #42427e" | zodbot
| style="color: #42427e" | Useful Commands: #action #agreed #halp #info #idea #link #topic.
|| [[#t16:00:24|16:00]]
|- id="t16:00:28"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | #meetingname fedora-qa
|| [[#t16:00:28|16:00]]
|- id="t16:00:28"
! style="background-color: #42427e" | zodbot
| style="color: #42427e" | The meeting name has been set to 'fedora-qa'
|| [[#t16:00:28|16:00]]
|- id="t16:00:31"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | #topic roll call
|| [[#t16:00:31|16:00]]
|- id="t16:00:38"
| colspan="2" | * jreznik is here
|| [[#t16:00:38|16:00]]
|- id="t16:00:46"
| colspan="2" | * satellit listening
|| [[#t16:00:46|16:00]]
|- id="t16:00:48"
| colspan="2" | * jsmith is lurking, and having internet issues
|| [[#t16:00:48|16:00]]
|- id="t16:00:52"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | welcome to the AGM of the grocery store bicyclists' association
|| [[#t16:00:52|16:00]]
|- id="t16:01:06"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | first on the order of business: raptor protection
|| [[#t16:01:06|16:01]]
|- id="t16:01:11"
| colspan="2" | * jskladan gets of his bike
|| [[#t16:01:11|16:01]]
|- id="t16:01:18"
| colspan="2" | * mkrizek is here
|| [[#t16:01:18|16:01]]
|- id="t16:01:31"
| colspan="2" | * j_dulaney waves
|| [[#t16:01:31|16:01]]
|- id="t16:01:32"
| colspan="2" | * jreznik has kickbike only (but the big one as he's big boy!)
|| [[#t16:01:32|16:01]]
|- id="t16:01:50"
! style="background-color: #818144" | jskladan
| style="color: #818144" | adamw: i'd say - don't let raptors pass the tests, but that would probably by rasistic...
|| [[#t16:01:50|16:01]]
|- id="t16:02:06"
! style="background-color: #854685" | j_dulaney
| style="color: #854685" | Raptors aint getting my bacon
|| [[#t16:02:06|16:02]]
|- id="t16:02:06"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | speciesist!
|| [[#t16:02:06|16:02]]
|- id="t16:02:16"
| colspan="2" | * j_dulaney brandishes rapier
|| [[#t16:02:16|16:02]]
|- id="t16:02:20"
! style="background-color: #818144" | jskladan
| style="color: #818144" | that ^^
|| [[#t16:02:20|16:02]]
|- id="t16:02:27"
| colspan="2" | * jsmith files a blocker bug against the raptor
|| [[#t16:02:27|16:02]]
|- id="t16:02:31"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | aside from the few cyclist-munching incidents and their tendency to arrive with significantly fewer passengers, raptors make fine bus drivers
|| [[#t16:02:31|16:02]]
|- id="t16:03:06"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | man, this is gonna look super-professional in the logs
|| [[#t16:03:06|16:03]]
|- id="t16:03:09"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | tflink: ping?
|| [[#t16:03:09|16:03]]
|- id="t16:03:13"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | i know you're around, stop hiding.
|| [[#t16:03:13|16:03]]
|- id="t16:03:29"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | don't leave me alone with all these Js.
|| [[#t16:03:29|16:03]]
|- id="t16:03:52"
| colspan="2" | * pschindl is here
|| [[#t16:03:52|16:03]]
|- id="t16:04:42"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | so no viking-ice, no tflink, no kparal? fired, the lot of 'em
|| [[#t16:04:42|16:04]]
|- id="t16:04:55"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | alrighty
|| [[#t16:04:55|16:04]]
|- id="t16:05:16"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | #topic Previous meeting follow-up
|| [[#t16:05:16|16:05]]
|- id="t16:05:50"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | "adamw to brief #fedora ops and fedora-user-list regulars on fedup" - heh.
|| [[#t16:05:50|16:05]]
|- id="t16:06:00"
! style="background-color: #488888" | tflink
| style="color: #488888" | sorry, trying to get the list ready for mini-blocker-review
|| [[#t16:06:00|16:06]]
|- id="t16:06:12"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | well, I've talked to a few people about it, not sure I hit everyone in the description
|| [[#t16:06:12|16:06]]
|- id="t16:06:20"
| colspan="2" | * maxamillion is here
|| [[#t16:06:20|16:06]]
|- id="t16:06:25"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | .fire tflink
|| [[#t16:06:25|16:06]]
|- id="t16:06:25"
! style="background-color: #42427e" | zodbot
| style="color: #42427e" | adamw fires tflink
|| [[#t16:06:25|16:06]]
|- id="t16:06:39"
! style="background-color: #854685" | j_dulaney
| style="color: #854685" | Heh.
|| [[#t16:06:39|16:06]]
|- id="t16:06:42"
! style="background-color: #488888" | tflink
| style="color: #488888" | cool, now I can go do other stuff
|| [[#t16:06:42|16:06]]
|- id="t16:06:45"
| colspan="2" | * maxamillion runs like hell from the angry bot master
|| [[#t16:06:45|16:06]]
|- id="t16:06:49"
! style="background-color: #854685" | j_dulaney
| style="color: #854685" | My greatest contribution to Fedora QA
|| [[#t16:06:49|16:06]]
|- id="t16:07:06"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | it will live on long beyond fedora QA.
|| [[#t16:07:06|16:07]]
|- id="t16:07:15"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | as long as adamw is firing stuff, a little piece of you will survive.
|| [[#t16:07:15|16:07]]
|- id="t16:07:27"
! style="background-color: #854685" | j_dulaney
| style="color: #854685" | Yes!
|| [[#t16:07:27|16:07]]
|- id="t16:07:55"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | so fenrus and bob from #fedora are kind of up on fedup and grumbling about it to wwoods. not sure about user-list folks. anyone been following that list lately?
|| [[#t16:07:55|16:07]]
|- id="t16:08:32"
! style="background-color: #488888" | tflink
| style="color: #488888" | not so much
|| [[#t16:08:32|16:08]]
|- id="t16:08:34"
! style="background-color: #8c4a4a" | BobJensen
| style="color: #8c4a4a" | I've nothing on fedup
|| [[#t16:08:34|16:08]]
|- id="t16:08:42"
! style="background-color: #488888" | tflink
| style="color: #488888" | but I keep seeing bugs about people using my siderepo
|| [[#t16:08:42|16:08]]
|- id="t16:08:58"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | BobJensen: oh sorry bob
|| [[#t16:08:58|16:08]]
|- id="t16:09:12"
! style="background-color: #488888" | tflink
| style="color: #488888" | which makes me think that I need to add something to the testing docs "don't use this for production instances, see the real docs"
|| [[#t16:09:12|16:09]]
|- id="t16:09:21"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | tflink: that sounds like a plan
|| [[#t16:09:21|16:09]]
|- id="t16:09:34"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | #action tflink to clarify use of his fedup side repo
|| [[#t16:09:34|16:09]]
|- id="t16:09:47"
! style="background-color: #8c4a4a" | BobJensen
| style="color: #8c4a4a" | I don't know that we have seen enough users of it honestly
|| [[#t16:09:47|16:09]]
|- id="t16:10:09"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | BobJensen: see https://fedoraproject.org/wiki/FedUp . it mostly works except when it doesn't.
|| [[#t16:10:09|16:10]]
|- id="t16:10:21"
! style="background-color: #854685" | j_dulaney
| style="color: #854685" | Still?
|| [[#t16:10:21|16:10]]
|- id="t16:10:31"
! style="background-color: #488888" | tflink
| style="color: #488888" | j_dulaney: still? it's brand new code
|| [[#t16:10:31|16:10]]
|- id="t16:10:33"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | BobJensen: the idea was we wanted to make sure you folks knew about fedup and could help people appropriately who try to use it, or asked 'how do i upgrade'
|| [[#t16:10:33|16:10]]
|- id="t16:10:44"
! style="background-color: #854685" | j_dulaney
| style="color: #854685" | Is it still doing the "not installing kernel" issue/
|| [[#t16:10:44|16:10]]
|- id="t16:10:49"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | j_dulaney: well, I mean, like all upgraders. i'd say the same about the old ones.
|| [[#t16:10:49|16:10]]
|- id="t16:10:51"
! style="background-color: #8c4a4a" | BobJensen
| style="color: #8c4a4a" | adamw: I'll add a shortcut here so if people ask I have the link anyhow
|| [[#t16:10:51|16:10]]
|- id="t16:11:06"
! style="background-color: #488888" | tflink
| style="color: #488888" | j_dulaney: pretty much, but that's not a fedup issue
|| [[#t16:11:06|16:11]]
|- id="t16:11:15"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | BobJensen: there's a 'how can I upgrade' anchor in the wiki page
|| [[#t16:11:15|16:11]]
|- id="t16:11:34"
! style="background-color: #854685" | j_dulaney
| style="color: #854685" | tflink:  You know what I think about that, I'll not start flamng here
|| [[#t16:11:34|16:11]]
|- id="t16:11:40"
| colspan="2" | * kparal arrives late
|| [[#t16:11:40|16:11]]
|- id="t16:12:16"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | okay, i'll brief bob a bit more in private and let's move on
|| [[#t16:12:16|16:12]]
|- id="t16:12:31"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | #info "adamw to brief #fedora ops and fedora-user-list regulars on fedup" - partly done
|| [[#t16:12:31|16:12]]
|- id="t16:12:44"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | #info "adamw to brief #fedora ops and fedora-user-list regulars on fedup" - done, and we'll come to it in a minute.
|| [[#t16:12:44|16:12]]
|- id="t16:12:46"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | grrr
|| [[#t16:12:46|16:12]]
|- id="t16:12:47"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | #undo
|| [[#t16:12:47|16:12]]
|- id="t16:12:47"
! style="background-color: #42427e" | zodbot
| style="color: #42427e" | Removing item from minutes: &lt;MeetBot.items.Info object at 0x29840e50&gt;
|| [[#t16:12:47|16:12]]
|- id="t16:12:54"
! style="background-color: #4b904b" | Martix
| style="color: #4b904b" | what are you doing here? let's /join #fedora-test-day :-P
|| [[#t16:12:54|16:12]]
|- id="t16:13:00"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | #info "adamw to put 'enterprise storage support in newui' on next week's agenda" - done, and we'll come to it in a minute.
|| [[#t16:13:00|16:13]]
|- id="t16:13:11"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | oh god, in 'things I forgot to blog about' news...
|| [[#t16:13:11|16:13]]
|- id="t16:13:22"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | #chair tflink kparal
|| [[#t16:13:22|16:13]]
|- id="t16:13:22"
! style="background-color: #42427e" | zodbot
| style="color: #42427e" | Current chairs: adamw kparal tflink
|| [[#t16:13:22|16:13]]
|- id="t16:13:34"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | #topic Fedora 18 Final status
|| [[#t16:13:34|16:13]]
|- id="t16:14:01"
! style="background-color: #4b904b" | Martix
| style="color: #4b904b" | adamw: you still can, test week just began
|| [[#t16:14:01|16:14]]
|- id="t16:14:21"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | so to make sure everyone's on the same page - the change deadline is now tomorrow, 2012-12-11
|| [[#t16:14:21|16:14]]
|- id="t16:14:33"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | the target release date is still 2012-01-08
|| [[#t16:14:33|16:14]]
|- id="t16:14:59"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | go/no-go is, conveniently, on new year's day, when we will all be fully alert and committed to such an important decision
|| [[#t16:14:59|16:14]]
|- id="t16:14:59"
! style="background-color: #488888" | tflink
| style="color: #488888" | with 28 proposed blockers and 14 accepted blockers? this should be interesting
|| [[#t16:14:59|16:14]]
|- id="t16:15:21"
! style="background-color: #854685" | j_dulaney
| style="color: #854685" | Heh
|| [[#t16:15:21|16:15]]
|- id="t16:15:31"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | #info current schedule: change deadlines 2012-12-11, go/no-go 2012-01-01, release date 2012-01-08
|| [[#t16:15:31|16:15]]
|- id="t16:15:36"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | tflink: fascinating!
|| [[#t16:15:36|16:15]]
|- id="t16:15:47"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | did you clean up the proposed list for the 'obvious' bugs?
|| [[#t16:15:47|16:15]]
|- id="t16:16:13"
! style="background-color: #4d4d93" | jreznik
| style="color: #4d4d93" | adamw: well, the go/no-go has to be definitely moved to thursday... but I'm not sure how final go/no-go looks like - it's on purpose on tuesday...
|| [[#t16:16:13|16:16]]
|- id="t16:16:17"
! style="background-color: #488888" | tflink
| style="color: #488888" | I got sidetracked this morning and haven't made it through the bugs that needed testing but I have a list of stuff that needs discussion
|| [[#t16:16:17|16:16]]
|- id="t16:16:22"
! style="background-color: #97974f" | maxamillion
| style="color: #97974f" | adamw: I have a prediction the the attendence to the go/no-go will be low ... pending the intensity of the hang overs
|| [[#t16:16:22|16:16]]
|- id="t16:17:17"
! style="background-color: #4d4d93" | jreznik
| style="color: #4d4d93" | so it would be 2013-01-03
|| [[#t16:17:17|16:17]]
|- id="t16:17:25"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | tflink: cool.
|| [[#t16:17:25|16:17]]
|- id="t16:17:34"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | jreznik: ah, okay.
|| [[#t16:17:34|16:17]]
|- id="t16:17:43"
! style="background-color: #97974f" | maxamillion
| style="color: #97974f" | (that was semi peanut gallery, semi serious)
|| [[#t16:17:43|16:17]]
|- id="t16:17:44"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | grr
|| [[#t16:17:44|16:17]]
|- id="t16:17:45"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | #undo
|| [[#t16:17:45|16:17]]
|- id="t16:17:45"
! style="background-color: #42427e" | zodbot
| style="color: #42427e" | Removing item from minutes: &lt;MeetBot.items.Info object at 0x226770d0&gt;
|| [[#t16:17:45|16:17]]
|- id="t16:17:53"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | #info current schedule: change deadlines 2012-12-11, go/no-go 2013-01-01, release date 2013-01-08
|| [[#t16:17:53|16:17]]
|- id="t16:18:04"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | #info go/no-go may move to 2013-01-03
|| [[#t16:18:04|16:18]]
|- id="t16:18:11"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | this is going to be tough enough without building a time machine. :)
|| [[#t16:18:11|16:18]]
|- id="t16:18:29"
! style="background-color: #854685" | j_dulaney
| style="color: #854685" | Heh
|| [[#t16:18:29|16:18]]
|- id="t16:18:46"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | #info Beta TC1 is out and in testing
|| [[#t16:18:46|16:18]]
|- id="t16:18:55"
! style="background-color: #4d4d93" | jreznik
| style="color: #4d4d93" | I'm really not sure why it's scheudled on tuesday... looking for veterans!
|| [[#t16:18:55|16:18]]
|- id="t16:18:56"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | no fires or explosions relating to TC1, right? it more or less works
|| [[#t16:18:56|16:18]]
|- id="t16:19:15"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | jreznik: hell if i know, i'm usually permanently wasted by this point in the schedule :P
|| [[#t16:19:15|16:19]]
|- id="t16:19:24"
| colspan="2" | * nirik has one thing to bring up at some point... lives are sometimes failing to compose... looks like a weird race condition or something.
|| [[#t16:19:24|16:19]]
|- id="t16:20:16"
! style="background-color: #854685" | j_dulaney
| style="color: #854685" | nirik:  With live-image-creator?
|| [[#t16:20:16|16:20]]
|- id="t16:20:23"
! style="background-color: #9b519b" | nirik
| style="color: #9b519b" | livecd-tools
|| [[#t16:20:23|16:20]]
|- id="t16:20:38"
! style="background-color: #9b519b" | nirik
| style="color: #9b519b" | https://bugzilla.redhat.com/show_bug.cgi?id=885385 is the bug.
|| [[#t16:20:38|16:20]]
|- id="t16:20:48"
| colspan="2" | * jreznik is reading
|| [[#t16:20:48|16:20]]
|- id="t16:21:36"
! style="background-color: #539e9e" | Viking-Ice
| style="color: #539e9e" | so we are suddenly back to 16:00 when last meeting was 17:00 utc?
|| [[#t16:21:36|16:21]]
|- id="t16:21:40"
! style="background-color: #9b519b" | nirik
| style="color: #9b519b" | I tweaked with the builders yesterday and they seem fine, so not sure what changed or whats causing it. ;(
|| [[#t16:21:40|16:21]]
|- id="t16:21:56"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | #info nirik found problems with live composes of Final - https://bugzilla.redhat.com/show_bug.cgi?id=885385
|| [[#t16:21:56|16:21]]
|- id="t16:22:02"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | Viking-Ice: er...it wasn't? we've been at 1600 the whole time?
|| [[#t16:22:02|16:22]]
|- id="t16:22:03"
! style="background-color: #854685" | j_dulaney
| style="color: #854685" | nirik:  It's only part of the time?
|| [[#t16:22:03|16:22]]
|- id="t16:22:15"
! style="background-color: #539e9e" | Viking-Ice
| style="color: #539e9e" | adamw, ah see it now blocker bug 17:00
|| [[#t16:22:15|16:22]]
|- id="t16:22:15"
! style="background-color: #a25555" | kparal
| style="color: #a25555" | Viking-Ice: qa meetings are at 16 utc, blocker bug meetings at 17 utc
|| [[#t16:22:15|16:22]]
|- id="t16:22:38"
! style="background-color: #854685" | j_dulaney
| style="color: #854685" | adamw:  It's always 11 am Eastern time, no matter if it is daylight savings or not
|| [[#t16:22:38|16:22]]
|- id="t16:22:42"
! style="background-color: #9b519b" | nirik
| style="color: #9b519b" | right. it seems unrelated to which ks is used... for example, the kde's failed this way for tc1... but later I did them over and they worked fine. I really don't get whats going wrong. ;(
|| [[#t16:22:42|16:22]]
|- id="t16:22:47"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | j_dulaney: yes, that's the idea.
|| [[#t16:22:47|16:22]]
|- id="t16:23:01"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | by 'whole time' i meant 'since the dst switch', of course.
|| [[#t16:23:01|16:23]]
|- id="t16:23:13"
! style="background-color: #854685" | j_dulaney
| style="color: #854685" | nirik:  Then we can probably live with it?
|| [[#t16:23:13|16:23]]
|- id="t16:23:26"
! style="background-color: #854685" | j_dulaney
| style="color: #854685" | nirik:  If at first you don't succeed, try again?
|| [[#t16:23:26|16:23]]
|- id="t16:23:29"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | #info no major showstoppers in TC1, it is viable for testing
|| [[#t16:23:29|16:23]]
|- id="t16:23:41"
! style="background-color: #9b519b" | nirik
| style="color: #9b519b" | well, I think that would be pretty poor for trying to compose things...
|| [[#t16:23:41|16:23]]
|- id="t16:24:00"
! style="background-color: #9b519b" | nirik
| style="color: #9b519b" | keep throwing it against the buildsystem until it works doesn't inspire confidence.
|| [[#t16:24:00|16:24]]
|- id="t16:24:07"
! style="background-color: #854685" | j_dulaney
| style="color: #854685" | Aye
|| [[#t16:24:07|16:24]]
|- id="t16:24:16"
! style="background-color: #4d4d93" | jreznik
| style="color: #4d4d93" | not good :( to just wait "to be lucky"
|| [[#t16:24:16|16:24]]
|- id="t16:24:28"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | but it works in a crisis.
|| [[#t16:24:28|16:24]]
|- id="t16:24:54"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | #info blocker list is considerable, though may be a little bit prunable
|| [[#t16:24:54|16:24]]
|- id="t16:25:19"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | tflink: how long is the list of bugs to discuss? should we do it inline or after the meeting?
|| [[#t16:25:19|16:25]]
|- id="t16:25:44"
| colspan="2" | * kparal is for a separate meeting
|| [[#t16:25:44|16:25]]
|- id="t16:25:52"
| colspan="2" | * j_dulaney notes he has a final exam in an hour
|| [[#t16:25:52|16:25]]
|- id="t16:26:10"
! style="background-color: #854685" | j_dulaney
| style="color: #854685" | So, by default I will be getting off in thirty minutes
|| [[#t16:26:10|16:26]]
|- id="t16:26:18"
! style="background-color: #488888" | tflink
| style="color: #488888" | I see 16 bugs on my list of 'ready for discussion'
|| [[#t16:26:18|16:26]]
|- id="t16:26:22"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | oh boy
|| [[#t16:26:22|16:26]]
|- id="t16:26:25"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | guess we're going 'after meeting'
|| [[#t16:26:25|16:26]]
|- id="t16:26:44"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | so aside from the above-noted...any major issues to resolve about 18 final status? or is everyone happy doing the blocker bug grind?
|| [[#t16:26:44|16:26]]
|- id="t16:28:13"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | or, you know, giving it all up to be a himalayan yak farmer.
|| [[#t16:28:13|16:28]]
|- id="t16:28:18"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | those are your only choices.
|| [[#t16:28:18|16:28]]
|- id="t16:28:29"
! style="background-color: #488888" | tflink
| style="color: #488888" | define "giving it all up"
|| [[#t16:28:29|16:28]]
|- id="t16:28:58"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | no. you must trust to the yaks.
|| [[#t16:28:58|16:28]]
|- id="t16:28:58"
! style="background-color: #854685" | j_dulaney
| style="color: #854685" | Do the criteria changes right quick
|| [[#t16:28:58|16:28]]
|- id="t16:28:59"
! style="background-color: #4d4d93" | jreznik
| style="color: #4d4d93" | yak farmer... nice dream
|| [[#t16:28:59|16:28]]
|- id="t16:29:09"
! style="background-color: #97974f" | maxamillion
| style="color: #97974f" | I've been really happy with F18's stability in the past week on my main workstation but I got lucky and didn't hit any anaconda bugs ... so blocker grind?
|| [[#t16:29:09|16:29]]
|- id="t16:29:15"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | j_dulaney: that's another topic
|| [[#t16:29:15|16:29]]
|- id="t16:29:16"
! style="background-color: #854685" | j_dulaney
| style="color: #854685" | Can I give it all up to be a pirate?
|| [[#t16:29:16|16:29]]
|- id="t16:29:47"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | maxam: blocker grind as in, find blocker bugs, test fixes, test TCs/RCs
|| [[#t16:29:47|16:29]]
|- id="t16:30:08"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | j_dulaney: you're allowed to be a pirate on days off from yak farming.
|| [[#t16:30:08|16:30]]
|- id="t16:30:28"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | oh yeah, i did put another bullet under this heading
|| [[#t16:30:28|16:30]]
|- id="t16:30:56"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | tflink: do you know what shape fedup is planned to be in for final?
|| [[#t16:30:56|16:30]]
|- id="t16:31:15"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | i'm guessing no GUI, but are the rough edges getting knocked off? manually specifying remote location, lack of progress etc
|| [[#t16:31:15|16:31]]
|- id="t16:31:27"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | and nirik: what was the SB status of TC1? I lost track of that
|| [[#t16:31:27|16:31]]
|- id="t16:32:00"
! style="background-color: #9b519b" | nirik
| style="color: #9b519b" | the signed shim is in updates-testing and was not pulled into the compose.
|| [[#t16:32:00|16:32]]
|- id="t16:32:14"
! style="background-color: #4d4d93" | jreznik
| style="color: #4d4d93" | adamw: for GUI - FESCo seems not to require it, what's in GIT is really really very early try
|| [[#t16:32:14|16:32]]
|- id="t16:32:45"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | nirik: okay, so no real SB support in TC1. might come in next build.
|| [[#t16:32:45|16:32]]
|- id="t16:32:59"
| colspan="2" | * nirik nods.
|| [[#t16:32:59|16:32]]
|- id="t16:33:00"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | #info TC1 is not signed for SB
|| [[#t16:33:00|16:33]]
|- id="t16:33:08"
! style="background-color: #9b519b" | nirik
| style="color: #9b519b" | if we pull new shim, we also need new lorax
|| [[#t16:33:08|16:33]]
|- id="t16:34:40"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | and vice versa?
|| [[#t16:34:40|16:34]]
|- id="t16:34:58"
! style="background-color: #854685" | j_dulaney
| style="color: #854685" | Shouldn't, I thought
|| [[#t16:34:58|16:34]]
|- id="t16:35:09"
! style="background-color: #854685" | j_dulaney
| style="color: #854685" | If I read things correctly
|| [[#t16:35:09|16:35]]
|- id="t16:35:17"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | istr nirik finding the build failed unless he pulled shim or downgraded something.
|| [[#t16:35:17|16:35]]
|- id="t16:35:31"
! style="background-color: #488888" | tflink
| style="color: #488888" | that was fun, lost network for a few minutes
|| [[#t16:35:31|16:35]]
|- id="t16:35:44"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | welcome back tflink. how are the yaks?
|| [[#t16:35:44|16:35]]
|- id="t16:35:47"
! style="background-color: #9b519b" | nirik
| style="color: #9b519b" | if we pull new lorax, it blows up without new shim
|| [[#t16:35:47|16:35]]
|- id="t16:35:49"
! style="background-color: #488888" | tflink
| style="color: #488888" | not shaven yet
|| [[#t16:35:49|16:35]]
|- id="t16:36:07"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | right.
|| [[#t16:36:07|16:36]]
|- id="t16:36:14"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | tflink: so i was just asking what the likely status of fedup for final is
|| [[#t16:36:14|16:36]]
|- id="t16:36:17"
! style="background-color: #97974f" | maxamillion
| style="color: #97974f" | nirik: is lorax the new pungi?
|| [[#t16:36:17|16:36]]
|- id="t16:36:29"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | as regards gui, 'smooth' operation, progress reporting
|| [[#t16:36:29|16:36]]
|- id="t16:36:35"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | maxam: they're both involved.
|| [[#t16:36:35|16:36]]
|- id="t16:36:36"
! style="background-color: #488888" | tflink
| style="color: #488888" | it's getting better but I'm a bit behind on my fedup testing ATM
|| [[#t16:36:36|16:36]]
|- id="t16:36:46"
! style="background-color: #97974f" | maxamillion
| style="color: #97974f" | adamw: rgtr
|| [[#t16:36:46|16:36]]
|- id="t16:36:48"
! style="background-color: #97974f" | maxamillion
| style="color: #97974f" | rgr*
|| [[#t16:36:48|16:36]]
|- id="t16:37:01"
! style="background-color: #488888" | tflink
| style="color: #488888" | my understanding is that there are some fixes in the pipeline that should help a few of the pain points
|| [[#t16:37:01|16:37]]
|- id="t16:37:01"
! style="background-color: #97974f" | maxamillion
| style="color: #97974f" | the whole shim madness is something I barely understand
|| [[#t16:37:01|16:37]]
|- id="t16:37:22"
! style="background-color: #4d4d93" | jreznik
| style="color: #4d4d93" | wwoods: are you around?
|| [[#t16:37:22|16:37]]
|- id="t16:37:25"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | maxam: i can forward you a gigantic email explanation of it i wrote if you like.
|| [[#t16:37:25|16:37]]
|- id="t16:37:35"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | #info some fixes for the rough edges of fedup impending
|| [[#t16:37:35|16:37]]
|- id="t16:37:42"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | okay, let's move on, time's a tickin
|| [[#t16:37:42|16:37]]
|- id="t16:37:50"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | #topic enterprise storage for F18/F19
|| [[#t16:37:50|16:37]]
|- id="t16:37:53"
! style="background-color: #57a657" | wwoods
| style="color: #57a657" | I'm around! I'm also about.
|| [[#t16:37:53|16:37]]
|- id="t16:37:53"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | Viking-Ice: around?
|| [[#t16:37:53|16:37]]
|- id="t16:37:56"
! style="background-color: #539e9e" | Viking-Ice
| style="color: #539e9e" | yup
|| [[#t16:37:56|16:37]]
|- id="t16:37:59"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | wwoods: too late!
|| [[#t16:37:59|16:37]]
|- id="t16:38:02"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | so this was yours...
|| [[#t16:38:02|16:38]]
|- id="t16:38:05"
! style="background-color: #57a657" | wwoods
| style="color: #57a657" | Well then I'm outside.
|| [[#t16:38:05|16:38]]
|- id="t16:38:09"
! style="background-color: #539e9e" | Viking-Ice
| style="color: #539e9e" | yup
|| [[#t16:38:09|16:38]]
|- id="t16:38:09"
! style="background-color: #57a657" | wwoods
| style="color: #57a657" | and other prepositions.
|| [[#t16:38:09|16:38]]
|- id="t16:38:12"
! style="background-color: #5959a9" | mjg59
| style="color: #5959a9" | (Crying)
|| [[#t16:38:12|16:38]]
|- id="t16:38:18"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | and, indeed, positions.
|| [[#t16:38:18|16:38]]
|- id="t16:38:32"
! style="background-color: #854685" | j_dulaney
| style="color: #854685" | adamw:  I'd like the shim email as well
|| [[#t16:38:32|16:38]]
|- id="t16:38:36"
! style="background-color: #854685" | j_dulaney
| style="color: #854685" | If you don't mind
|| [[#t16:38:36|16:38]]
|- id="t16:38:50"
! style="background-color: #539e9e" | Viking-Ice
| style="color: #539e9e" | https://www.redhat.com/archives/anaconda-devel-list/2012-December/msg00025.html
|| [[#t16:38:50|16:38]]
|- id="t16:38:50"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | mjg59: was that email I CCed you on too outrageously inaccurate or anything? before i send it to anyone else
|| [[#t16:38:50|16:38]]
|- id="t16:39:34"
! style="background-color: #4d4d93" | jreznik
| style="color: #4d4d93" | wwoods: (about dialog) - seems like there's another topic but if you have anything for fedup status - just fire it :)
|| [[#t16:39:34|16:39]]
|- id="t16:40:05"
! style="background-color: #5959a9" | mjg59
| style="color: #5959a9" | adamw: No, it seemed reasonable
|| [[#t16:40:05|16:40]]
|- id="t16:40:08"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | Viking-Ice: what was the outcome of that? iirc, 'advanced' storage types that require interaction to enable aren't going to work in F18
|| [[#t16:40:08|16:40]]
|- id="t16:40:11"
! style="background-color: #539e9e" | Viking-Ice
| style="color: #539e9e" | basically there is no UI on newUI for Enterprise/Advantage storage so enterprise admins/users will have to rely ks only
|| [[#t16:40:11|16:40]]
|- id="t16:40:12"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | mjg59: cool.
|| [[#t16:40:12|16:40]]
|- id="t16:40:43"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | #info enterprise/advanced storage types that require interaction to enable/use will not work via UI in in F18, but can be used via kickstart. UI is scheduled to re-appear in F19
|| [[#t16:40:43|16:40]]
|- id="t16:41:21"
! style="background-color: #539e9e" | Viking-Ice
| style="color: #539e9e" | this ofcourse is something that needs to be mentioned in the release notes
|| [[#t16:41:21|16:41]]
|- id="t16:41:40"
! style="background-color: #854685" | j_dulaney
| style="color: #854685" | +1
|| [[#t16:41:40|16:41]]
|- id="t16:41:55"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | agreed
|| [[#t16:41:55|16:41]]
|- id="t16:41:56"
! style="background-color: #539e9e" | Viking-Ice
| style="color: #539e9e" | not sure if there is specific Anaconda/Installer section in the release notes
|| [[#t16:41:56|16:41]]
|- id="t16:42:03"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | do you want a #action to let the docs team know about it?
|| [[#t16:42:03|16:42]]
|- id="t16:42:11"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | or i can take it if you like
|| [[#t16:42:11|16:42]]
|- id="t16:42:21"
! style="background-color: #539e9e" | Viking-Ice
| style="color: #539e9e" | no I'll handle it
|| [[#t16:42:21|16:42]]
|- id="t16:42:25"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | ok
|| [[#t16:42:25|16:42]]
|- id="t16:42:37"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | #action viking-ice to let docs team know about advanced storage for release notes
|| [[#t16:42:37|16:42]]
|- id="t16:42:52"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | anything else to cover on this or shall we move on to criteria/test cases?
|| [[#t16:42:52|16:42]]
|- id="t16:42:57"
| colspan="2" | * jreznik will recheck RN notes for it
|| [[#t16:42:57|16:42]]
|- id="t16:45:10"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | #topic Test case / criteria revision
|| [[#t16:45:10|16:45]]
|- id="t16:45:45"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | so i think my proposal on the RPM package error criterion was positively received, i'll go ahead and put that into production
|| [[#t16:45:45|16:45]]
|- id="t16:45:53"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | #action adamw to put packaging error criterion revision into production
|| [[#t16:45:53|16:45]]
|- id="t16:46:09"
! style="background-color: #854685" | j_dulaney
| style="color: #854685" | +1
|| [[#t16:46:09|16:46]]
|- id="t16:46:27"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | kparal's kickstart revision proposal spawned a big discussion which was interesting but might have stranded the proposal a bit
|| [[#t16:46:27|16:46]]
|- id="t16:46:42"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | any ideas for action there? try and reset the discussion to a list of ks parameters it's plausible to 'support' for f18?
|| [[#t16:46:42|16:46]]
|- id="t16:47:13"
! style="background-color: #a25555" | kparal
| style="color: #a25555" | I think we should vote in F18 according to our best conscience and target this new criterion to F19
|| [[#t16:47:13|16:47]]
|- id="t16:47:26"
! style="background-color: #854685" | j_dulaney
| style="color: #854685" | Aye, that would be a good move
|| [[#t16:47:26|16:47]]
|- id="t16:47:36"
! style="background-color: #a25555" | kparal
| style="color: #a25555" | it will be a long discussion yet, I think
|| [[#t16:47:36|16:47]]
|- id="t16:48:01"
! style="background-color: #854685" | j_dulaney
| style="color: #854685" | Actually, I really think that criterion revisions should not take effect until the *next* release
|| [[#t16:48:01|16:48]]
|- id="t16:48:19"
! style="background-color: #488888" | tflink
| style="color: #488888" | ideally, yes
|| [[#t16:48:19|16:48]]
|- id="t16:48:29"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | viking's said the same thing
|| [[#t16:48:29|16:48]]
|- id="t16:48:43"
! style="background-color: #854685" | j_dulaney
| style="color: #854685" | That's been my problem with all the criterion changes in the middle of this release
|| [[#t16:48:43|16:48]]
|- id="t16:48:45"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | i don't disagree in theory, but for f18, we've kinda had to rejig things on the run or else we'd have nothing applicable
|| [[#t16:48:45|16:48]]
|- id="t16:49:01"
! style="background-color: #4d4d93" | jreznik
| style="color: #4d4d93" | adamw: +1
|| [[#t16:49:01|16:49]]
|- id="t16:49:26"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | #action kparal to try and 'reset' kickstart criterion discussion back to the proposed set of 'supported' commands
|| [[#t16:49:26|16:49]]
|- id="t16:49:38"
! style="background-color: #a25555" | kparal
| style="color: #a25555" | hmm
|| [[#t16:49:38|16:49]]
|- id="t16:49:46"
! style="background-color: #539e9e" | Viking-Ice
| style="color: #539e9e" | can we actually do that
|| [[#t16:49:46|16:49]]
|- id="t16:49:47"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | that okay?
|| [[#t16:49:47|16:49]]
|- id="t16:49:47"
! style="background-color: #a25555" | kparal
| style="color: #a25555" | I can try
|| [[#t16:49:47|16:49]]
|- id="t16:50:00"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | Viking-Ice: sorry, actually do what?
|| [[#t16:50:00|16:50]]
|- id="t16:50:01"
! style="background-color: #539e9e" | Viking-Ice
| style="color: #539e9e" | dont we just need to say all ks command have to work and test for those
|| [[#t16:50:01|16:50]]
|- id="t16:50:18"
! style="background-color: #488888" | tflink
| style="color: #488888" | I'm not sure that's practical for F18
|| [[#t16:50:18|16:50]]
|- id="t16:50:21"
! style="background-color: #539e9e" | Viking-Ice
| style="color: #539e9e" | why try to split it up? ( should be easy to test as well )
|| [[#t16:50:21|16:50]]
|- id="t16:50:23"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | well the worry is that if we say that we'll find a bunch of fairly obscure bugs and then what?
|| [[#t16:50:23|16:50]]
|- id="t16:50:34"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | but i suppose we could do it that way around...test it and see how bad it is
|| [[#t16:50:34|16:50]]
|- id="t16:50:38"
! style="background-color: #539e9e" | Viking-Ice
| style="color: #539e9e" | let anaconda deal with it
|| [[#t16:50:38|16:50]]
|- id="t16:50:44"
! style="background-color: #854685" | j_dulaney
| style="color: #854685" | Heh
|| [[#t16:50:44|16:50]]
|- id="t16:50:46"
! style="background-color: #539e9e" | Viking-Ice
| style="color: #539e9e" | it's their brokenness right
|| [[#t16:50:46|16:50]]
|- id="t16:51:01"
! style="background-color: #a25555" | kparal
| style="color: #a25555" | adamw: well we can always waive some obscure problems, same as for graphics cards etc
|| [[#t16:51:01|16:51]]
|- id="t16:51:12"
! style="background-color: #854685" | j_dulaney
| style="color: #854685" | Aye
|| [[#t16:51:12|16:51]]
|- id="t16:51:24"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | kparal: well we can do that because they're 'conditional' breakages
|| [[#t16:51:24|16:51]]
|- id="t16:51:28"
! style="background-color: #a25555" | kparal
| style="color: #a25555" | but it becomes more tricky than with a defined set
|| [[#t16:51:28|16:51]]
|- id="t16:51:32"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | we don't have a criterion that says 'all graphics cards have to work'
|| [[#t16:51:32|16:51]]
|- id="t16:51:34"
! style="background-color: #854685" | j_dulaney
| style="color: #854685" | "All KS commands should work unless they are really freaking off the wall"
|| [[#t16:51:34|16:51]]
|- id="t16:51:41"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | if we did, it'd be kinda hard to waive some graphics cards being broken :)
|| [[#t16:51:41|16:51]]
|- id="t16:51:45"
! style="background-color: #539e9e" | Viking-Ice
| style="color: #539e9e" | unless they have spesific ks command that can never break or become backwards incompatible I cant see how we can
|| [[#t16:51:45|16:51]]
|- id="t16:51:56"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | so if we have a criterion that says 'all kickstart commands have to work', it seems quite hard for us to say 'well except THIS one, obviously!'
|| [[#t16:51:56|16:51]]
|- id="t16:52:06"
! style="background-color: #539e9e" | Viking-Ice
| style="color: #539e9e" | so basically we should follow their list ( if exist ) or check for all existing supporting ks commands right?
|| [[#t16:52:06|16:52]]
|- id="t16:52:31"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | Viking-Ice: that was matt miller's idea, and it seems reasonable, but the problem is right now the documentation of kickstart commands is somewhat outdated and doesn't in any way define a 'core set'
|| [[#t16:52:31|16:52]]
|- id="t16:52:37"
! style="background-color: #a25555" | kparal
| style="color: #a25555" | that goes back to my long-term complain about criteria being all-or-nothing game
|| [[#t16:52:37|16:52]]
|- id="t16:52:39"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | so for f18, it's a bit hard
|| [[#t16:52:39|16:52]]
|- id="t16:52:50"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | sigh, we seem to keep winding up on tangents here
|| [[#t16:52:50|16:52]]
|- id="t16:53:03"
! style="background-color: #a25555" | kparal
| style="color: #a25555" | I'll try to restart the discussion
|| [[#t16:53:03|16:53]]
|- id="t16:53:11"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | the task is really just 'quantify the level of kickstart functionality we consider minimal for f18 final release', that does not seem like it should be impossible
|| [[#t16:53:11|16:53]]
|- id="t16:53:12"
! style="background-color: #a25555" | kparal
| style="color: #a25555" | with just a core set of commands for F18
|| [[#t16:53:12|16:53]]
|- id="t16:53:17"
! style="background-color: #a25555" | kparal
| style="color: #a25555" | and possible changes for F19
|| [[#t16:53:17|16:53]]
|- id="t16:53:18"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | and shouldn't require fundamental reimaginings of process or anything
|| [[#t16:53:18|16:53]]
|- id="t16:53:36"
! style="background-color: #539e9e" | Viking-Ice
| style="color: #539e9e" | yes I just fail to see why the need to quantify it in the first place
|| [[#t16:53:36|16:53]]
|- id="t16:54:14"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | what's your alternative for dealing with whether breakages in kickstart should block f18 final?
|| [[#t16:54:14|16:54]]
|- id="t16:54:18"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | just do it case-by-case?
|| [[#t16:54:18|16:54]]
|- id="t16:54:27"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | i mean, we could do that.
|| [[#t16:54:27|16:54]]
|- id="t16:54:40"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | we could just say 'we don't want to fiddle with the criteria temporarily, so we'll just handle these one by one for now.'
|| [[#t16:54:40|16:54]]
|- id="t16:54:52"
! style="background-color: #539e9e" | Viking-Ice
| style="color: #539e9e" | I would say it blocks always and questionable items dealt with on case by case bases
|| [[#t16:54:52|16:54]]
|- id="t16:54:55"
! style="background-color: #4d4d93" | jreznik
| style="color: #4d4d93" | case by case could work for F18, especially as we do not know in what state it is...
|| [[#t16:54:55|16:54]]
|- id="t16:55:56"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | shall we go with that, then? seems straightforward
|| [[#t16:55:56|16:55]]
|- id="t16:56:30"
! style="background-color: #488888" | tflink
| style="color: #488888" | it'll work, I suppose and will probably generate less discussion in the short term
|| [[#t16:56:30|16:56]]
|- id="t16:56:49"
! style="background-color: #488888" | tflink
| style="color: #488888" | may lead to some interesting discussions about what is worth blocking for, though :)
|| [[#t16:56:49|16:56]]
|- id="t16:56:50"
! style="background-color: #a25555" | kparal
| style="color: #a25555" | case by case is the best way, it just requires more time to discuss
|| [[#t16:56:50|16:56]]
|- id="t16:56:59"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | okay. well let's hope we don't get too many cases. :)
|| [[#t16:56:59|16:56]]
|- id="t16:57:01"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | #undo
|| [[#t16:57:01|16:57]]
|- id="t16:57:01"
! style="background-color: #42427e" | zodbot
| style="color: #42427e" | Removing item from minutes: &lt;MeetBot.items.Action object at 0x1f3f3e10&gt;
|| [[#t16:57:01|16:57]]
|- id="t16:57:17"
! style="background-color: #a25555" | kparal
| style="color: #a25555" | adamw: should we follow up on that discussion for F19?
|| [[#t16:57:17|16:57]]
|- id="t16:57:33"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | #agreed instead of trying to write a 'temporary criterion' we'll deal with kickstart proposed blockers on a case-by-case basis for F18 final and try to come up with a longer-term criterion for F19+
|| [[#t16:57:33|16:57]]
|- id="t16:57:36"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | I think so, yeah.
|| [[#t16:57:36|16:57]]
|- id="t16:57:39"
! style="background-color: #a25555" | kparal
| style="color: #a25555" | ok
|| [[#t16:57:39|16:57]]
|- id="t16:57:40"
! style="background-color: #854685" | j_dulaney
| style="color: #854685" | kparal That would be a good idea
|| [[#t16:57:40|16:57]]
|- id="t16:57:43"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | you want to do that now or keep it for post-release?
|| [[#t16:57:43|16:57]]
|- id="t16:57:51"
! style="background-color: #488888" | tflink
| style="color: #488888" | we might want to tell the anaconda devs what we're doing, though
|| [[#t16:57:51|16:57]]
|- id="t16:57:59"
| colspan="2" | * j_dulaney needs to be off for his final final
|| [[#t16:57:59|16:57]]
|- id="t16:57:59"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | yeah, and follow up on test list
|| [[#t16:57:59|16:57]]
|- id="t16:58:03"
! style="background-color: #a25555" | kparal
| style="color: #a25555" | adamw: I'll write a note there
|| [[#t16:58:03|16:58]]
|- id="t16:58:13"
! style="background-color: #854685" | j_dulaney
| style="color: #854685" | See y'all later.
|| [[#t16:58:13|16:58]]
|- id="t16:58:15"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | #action kparal to follow up on test@ discussion to explain the plan, and let anaconda team know
|| [[#t16:58:15|16:58]]
|- id="t16:58:16"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | cya dulaney
|| [[#t16:58:16|16:58]]
|- id="t16:58:46"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | okey dokey
|| [[#t16:58:46|16:58]]
|- id="t16:58:55"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | pschindl: are you planning to work on the issues identified in your test case / criteria survey?
|| [[#t16:58:55|16:58]]
|- id="t16:59:50"
! style="background-color: #adad5b" | pschindl
| style="color: #adad5b" | adamw: yes
|| [[#t16:59:50|16:59]]
|- id="t17:00:07"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | cool
|| [[#t17:00:07|17:00]]
|- id="t17:00:13"
! style="background-color: #adad5b" | pschindl
| style="color: #adad5b" | I'd like to go through it this week
|| [[#t17:00:13|17:00]]
|- id="t17:00:21"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | did anyone have any worries / questions about pschindl's proposals that haven't been brought up in the thread?
|| [[#t17:00:21|17:00]]
|- id="t17:01:39"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | #info pschindl will work on his proposed final test case changes (see thread 'Final criteria/Test cases interconnection')
|| [[#t17:01:39|17:01]]
|- id="t17:01:43"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | #topic open floor
|| [[#t17:01:43|17:01]]
|- id="t17:01:47"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | anyone have anything that wasn't covered?
|| [[#t17:01:47|17:01]]
|- id="t17:03:08"
| colspan="2" | * satellit needed; a good anaconda tutorial  lots of people having problems understanding how to install
|| [[#t17:03:08|17:03]]
|- id="t17:03:30"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | the docs team are working on updating the install guide for newUI.
|| [[#t17:03:30|17:03]]
|- id="t17:03:56"
! style="background-color: #488888" | tflink
| style="color: #488888" | and people having trouble with patience, aparrently
|| [[#t17:03:56|17:03]]
|- id="t17:04:02"
! style="background-color: #b15db1" | satellit
| style="color: #b15db1" | +1
|| [[#t17:04:02|17:04]]
|- id="t17:05:04"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | tflink: where are we doing the blocker review this week?
|| [[#t17:05:04|17:05]]
|- id="t17:05:19"
! style="background-color: #488888" | tflink
| style="color: #488888" | bugzappers, I think unless someone has a better idea
|| [[#t17:05:19|17:05]]
|- id="t17:05:33"
| colspan="2" | * kparal +1
|| [[#t17:05:33|17:05]]
|- id="t17:05:58"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | okey dokey
|| [[#t17:05:58|17:05]]
|- id="t17:06:08"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | everyone to #fedora-bugzappers for some thrilling blocker review in two minutes
|| [[#t17:06:08|17:06]]
|- id="t17:06:13"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | or, you know, head for the yaks
|| [[#t17:06:13|17:06]]
|- id="t17:06:18"
| colspan="2" | * adamw sets fuse for two minutes
|| [[#t17:06:18|17:06]]
|- id="t17:06:25"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | it's a classical physics fuse this week!
|| [[#t17:06:25|17:06]]
|- id="t17:06:57"
! style="background-color: #539e9e" | Viking-Ice
| style="color: #539e9e" | It should be done in QA or someother channel then bugzappers
|| [[#t17:06:57|17:06]]
|- id="t17:07:42"
! style="background-color: #a25555" | kparal
| style="color: #a25555" | it should be done in #fedora-anythingelsethanbugzappers, right?
|| [[#t17:07:42|17:07]]
|- id="t17:07:56"
! style="background-color: #539e9e" | Viking-Ice
| style="color: #539e9e" | I still say QA
|| [[#t17:07:56|17:07]]
|- id="t17:08:04"
! style="background-color: #a25555" | kparal
| style="color: #a25555" | -1
|| [[#t17:08:04|17:08]]
|- id="t17:08:10"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | thanks folks
|| [[#t17:08:10|17:08]]
|- id="t17:08:11"
! style="background-color: #539e9e" | Viking-Ice
| style="color: #539e9e" | but I accept  #fedora-anythingelsethanbugzappers as well
|| [[#t17:08:11|17:08]]
|- id="t17:08:12"
! style="background-color: #407a40" | adamw
| style="color: #407a40" | #endmeeting
|| [[#t17:08:12|17:08]]
|}
Generated by irclog2html.py 2.11.0 by [mailto:marius@pov.lt Marius Gedminas] - find it at [http://mg.pov.lt/irclog2html mg.pov.lt]!

Latest revision as of 05:02, 31 January 2013

Attendees

  • adamw (150)
  • j_dulaney (36)
  • tflink (22)
  • Viking-Ice (21)
  • kparal (20)
  • jreznik (14)
  • nirik (11)
  • maxamillion (9)
  • zodbot (8)
  • jskladan (3)
  • wwoods (3)
  • satellit (3)
  • BobJensen (3)
  • pschindl (3)
  • mjg59 (2)
  • Martix (2)
  • jsmith (2)
  • mkrizek (1)

Agenda

  • Previous meeting follow-up
  • Fedora 18 Final status
  • Enterprise storage support for F18 / F19
  • Test case / criteria revision
  • Open floor

Previous meeting follow-up

  • adamw to brief #fedora ops and fedora-user-list regulars on fedup - he talked to some people, maybe not everyone
  • adamw to put 'enterprise storage support in newui' on next week's agenda - done!

Fedora 18 Final status

  • Current schedule was: change deadlines 2012-12-11, go/no-go 2012-01-01, release date 2012-01-08
  • Final TC1 was available and viable for testing, but not Secure Boot-enabled
  • Blocker list was substantial, at 28 proposed
  • fedup GUI still was not available, some fixes for rough edges pending

Enterprise storage support for F18 / F19

  • Enterprise/advanced storage types that require interaction to enable/use would not work via UI in in F18, but could be used via kickstart. UI is scheduled to re-appear in F19
  • Agreed that this needed to be documented for final release

Test case / criteria revision

  • RPM package error proposal positively received, should be put into practice
  • Agreed that we couldn't agree on a kickstart criterion, instead agreed to handle kickstart bugs on a case-by-case basis for F18
  • pschindl was working on test case adjustments for Final

Open floor

N/A

Action items

  • tflink to clarify use of his fedup side repo
  • viking-ice to let docs team know about advanced storage for release notes
  • adamw to put packaging error criterion revision into production
  • kparal to follow up on test@ discussion to explain the plan, and let anaconda team know

IRC Log

adamw #startmeeting Fedora QA meeting 16:00
zodbot Meeting started Mon Dec 10 16:00:24 2012 UTC. The chair is adamw. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00
zodbot Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00
adamw #meetingname fedora-qa 16:00
zodbot The meeting name has been set to 'fedora-qa' 16:00
adamw #topic roll call 16:00
* jreznik is here 16:00
* satellit listening 16:00
* jsmith is lurking, and having internet issues 16:00
adamw welcome to the AGM of the grocery store bicyclists' association 16:00
adamw first on the order of business: raptor protection 16:01
* jskladan gets of his bike 16:01
* mkrizek is here 16:01
* j_dulaney waves 16:01
* jreznik has kickbike only (but the big one as he's big boy!) 16:01
jskladan adamw: i'd say - don't let raptors pass the tests, but that would probably by rasistic... 16:01
j_dulaney Raptors aint getting my bacon 16:02
adamw speciesist! 16:02
* j_dulaney brandishes rapier 16:02
jskladan that ^^ 16:02
* jsmith files a blocker bug against the raptor 16:02
adamw aside from the few cyclist-munching incidents and their tendency to arrive with significantly fewer passengers, raptors make fine bus drivers 16:02
adamw man, this is gonna look super-professional in the logs 16:03
adamw tflink: ping? 16:03
adamw i know you're around, stop hiding. 16:03
adamw don't leave me alone with all these Js. 16:03
* pschindl is here 16:03
adamw so no viking-ice, no tflink, no kparal? fired, the lot of 'em 16:04
adamw alrighty 16:04
adamw #topic Previous meeting follow-up 16:05
adamw "adamw to brief #fedora ops and fedora-user-list regulars on fedup" - heh. 16:05
tflink sorry, trying to get the list ready for mini-blocker-review 16:06
adamw well, I've talked to a few people about it, not sure I hit everyone in the description 16:06
* maxamillion is here 16:06
adamw .fire tflink 16:06
zodbot adamw fires tflink 16:06
j_dulaney Heh. 16:06
tflink cool, now I can go do other stuff 16:06
* maxamillion runs like hell from the angry bot master 16:06
j_dulaney My greatest contribution to Fedora QA 16:06
adamw it will live on long beyond fedora QA. 16:07
adamw as long as adamw is firing stuff, a little piece of you will survive. 16:07
j_dulaney Yes! 16:07
adamw so fenrus and bob from #fedora are kind of up on fedup and grumbling about it to wwoods. not sure about user-list folks. anyone been following that list lately? 16:07
tflink not so much 16:08
BobJensen I've nothing on fedup 16:08
tflink but I keep seeing bugs about people using my siderepo 16:08
adamw BobJensen: oh sorry bob 16:08
tflink which makes me think that I need to add something to the testing docs "don't use this for production instances, see the real docs" 16:09
adamw tflink: that sounds like a plan 16:09
adamw #action tflink to clarify use of his fedup side repo 16:09
BobJensen I don't know that we have seen enough users of it honestly 16:09
adamw BobJensen: see https://fedoraproject.org/wiki/FedUp . it mostly works except when it doesn't. 16:10
j_dulaney Still? 16:10
tflink j_dulaney: still? it's brand new code 16:10
adamw BobJensen: the idea was we wanted to make sure you folks knew about fedup and could help people appropriately who try to use it, or asked 'how do i upgrade' 16:10
j_dulaney Is it still doing the "not installing kernel" issue/ 16:10
adamw j_dulaney: well, I mean, like all upgraders. i'd say the same about the old ones. 16:10
BobJensen adamw: I'll add a shortcut here so if people ask I have the link anyhow 16:10
tflink j_dulaney: pretty much, but that's not a fedup issue 16:11
adamw BobJensen: there's a 'how can I upgrade' anchor in the wiki page 16:11
j_dulaney tflink: You know what I think about that, I'll not start flamng here 16:11
* kparal arrives late 16:11
adamw okay, i'll brief bob a bit more in private and let's move on 16:12
adamw #info "adamw to brief #fedora ops and fedora-user-list regulars on fedup" - partly done 16:12
adamw #info "adamw to brief #fedora ops and fedora-user-list regulars on fedup" - done, and we'll come to it in a minute. 16:12
adamw grrr 16:12
adamw #undo 16:12
zodbot Removing item from minutes: <MeetBot.items.Info object at 0x29840e50> 16:12
Martix what are you doing here? let's /join #fedora-test-day :-P 16:12
adamw #info "adamw to put 'enterprise storage support in newui' on next week's agenda" - done, and we'll come to it in a minute. 16:13
adamw oh god, in 'things I forgot to blog about' news... 16:13
adamw #chair tflink kparal 16:13
zodbot Current chairs: adamw kparal tflink 16:13
adamw #topic Fedora 18 Final status 16:13
Martix adamw: you still can, test week just began 16:14
adamw so to make sure everyone's on the same page - the change deadline is now tomorrow, 2012-12-11 16:14
adamw the target release date is still 2012-01-08 16:14
adamw go/no-go is, conveniently, on new year's day, when we will all be fully alert and committed to such an important decision 16:14
tflink with 28 proposed blockers and 14 accepted blockers? this should be interesting 16:14
j_dulaney Heh 16:15
adamw #info current schedule: change deadlines 2012-12-11, go/no-go 2012-01-01, release date 2012-01-08 16:15
adamw tflink: fascinating! 16:15
adamw did you clean up the proposed list for the 'obvious' bugs? 16:15
jreznik adamw: well, the go/no-go has to be definitely moved to thursday... but I'm not sure how final go/no-go looks like - it's on purpose on tuesday... 16:16
tflink I got sidetracked this morning and haven't made it through the bugs that needed testing but I have a list of stuff that needs discussion 16:16
maxamillion adamw: I have a prediction the the attendence to the go/no-go will be low ... pending the intensity of the hang overs 16:16
jreznik so it would be 2013-01-03 16:17
adamw tflink: cool. 16:17
adamw jreznik: ah, okay. 16:17
maxamillion (that was semi peanut gallery, semi serious) 16:17
adamw grr 16:17
adamw #undo 16:17
zodbot Removing item from minutes: <MeetBot.items.Info object at 0x226770d0> 16:17
adamw #info current schedule: change deadlines 2012-12-11, go/no-go 2013-01-01, release date 2013-01-08 16:17
adamw #info go/no-go may move to 2013-01-03 16:18
adamw this is going to be tough enough without building a time machine. :) 16:18
j_dulaney Heh 16:18
adamw #info Beta TC1 is out and in testing 16:18
jreznik I'm really not sure why it's scheudled on tuesday... looking for veterans! 16:18
adamw no fires or explosions relating to TC1, right? it more or less works 16:18
adamw jreznik: hell if i know, i'm usually permanently wasted by this point in the schedule :P 16:19
* nirik has one thing to bring up at some point... lives are sometimes failing to compose... looks like a weird race condition or something. 16:19
j_dulaney nirik: With live-image-creator? 16:20
nirik livecd-tools 16:20
nirik https://bugzilla.redhat.com/show_bug.cgi?id=885385 is the bug. 16:20
* jreznik is reading 16:20
Viking-Ice so we are suddenly back to 16:00 when last meeting was 17:00 utc? 16:21
nirik I tweaked with the builders yesterday and they seem fine, so not sure what changed or whats causing it. ;( 16:21
adamw #info nirik found problems with live composes of Final - https://bugzilla.redhat.com/show_bug.cgi?id=885385 16:21
adamw Viking-Ice: er...it wasn't? we've been at 1600 the whole time? 16:22
j_dulaney nirik: It's only part of the time? 16:22
Viking-Ice adamw, ah see it now blocker bug 17:00 16:22
kparal Viking-Ice: qa meetings are at 16 utc, blocker bug meetings at 17 utc 16:22
j_dulaney adamw: It's always 11 am Eastern time, no matter if it is daylight savings or not 16:22
nirik right. it seems unrelated to which ks is used... for example, the kde's failed this way for tc1... but later I did them over and they worked fine. I really don't get whats going wrong. ;( 16:22
adamw j_dulaney: yes, that's the idea. 16:22
adamw by 'whole time' i meant 'since the dst switch', of course. 16:23
j_dulaney nirik: Then we can probably live with it? 16:23
j_dulaney nirik: If at first you don't succeed, try again? 16:23
adamw #info no major showstoppers in TC1, it is viable for testing 16:23
nirik well, I think that would be pretty poor for trying to compose things... 16:23
nirik keep throwing it against the buildsystem until it works doesn't inspire confidence. 16:24
j_dulaney Aye 16:24
jreznik not good :( to just wait "to be lucky" 16:24
adamw but it works in a crisis. 16:24
adamw #info blocker list is considerable, though may be a little bit prunable 16:24
adamw tflink: how long is the list of bugs to discuss? should we do it inline or after the meeting? 16:25
* kparal is for a separate meeting 16:25
* j_dulaney notes he has a final exam in an hour 16:25
j_dulaney So, by default I will be getting off in thirty minutes 16:26
tflink I see 16 bugs on my list of 'ready for discussion' 16:26
adamw oh boy 16:26
adamw guess we're going 'after meeting' 16:26
adamw so aside from the above-noted...any major issues to resolve about 18 final status? or is everyone happy doing the blocker bug grind? 16:26
adamw or, you know, giving it all up to be a himalayan yak farmer. 16:28
adamw those are your only choices. 16:28
tflink define "giving it all up" 16:28
adamw no. you must trust to the yaks. 16:28
j_dulaney Do the criteria changes right quick 16:28
jreznik yak farmer... nice dream 16:28
maxamillion I've been really happy with F18's stability in the past week on my main workstation but I got lucky and didn't hit any anaconda bugs ... so blocker grind? 16:29
adamw j_dulaney: that's another topic 16:29
j_dulaney Can I give it all up to be a pirate? 16:29
adamw maxam: blocker grind as in, find blocker bugs, test fixes, test TCs/RCs 16:29
adamw j_dulaney: you're allowed to be a pirate on days off from yak farming. 16:30
adamw oh yeah, i did put another bullet under this heading 16:30
adamw tflink: do you know what shape fedup is planned to be in for final? 16:30
adamw i'm guessing no GUI, but are the rough edges getting knocked off? manually specifying remote location, lack of progress etc 16:31
adamw and nirik: what was the SB status of TC1? I lost track of that 16:31
nirik the signed shim is in updates-testing and was not pulled into the compose. 16:32
jreznik adamw: for GUI - FESCo seems not to require it, what's in GIT is really really very early try 16:32
adamw nirik: okay, so no real SB support in TC1. might come in next build. 16:32
* nirik nods. 16:32
adamw #info TC1 is not signed for SB 16:33
nirik if we pull new shim, we also need new lorax 16:33
adamw and vice versa? 16:34
j_dulaney Shouldn't, I thought 16:34
j_dulaney If I read things correctly 16:35
adamw istr nirik finding the build failed unless he pulled shim or downgraded something. 16:35
tflink that was fun, lost network for a few minutes 16:35
adamw welcome back tflink. how are the yaks? 16:35
nirik if we pull new lorax, it blows up without new shim 16:35
tflink not shaven yet 16:35
adamw right. 16:36
adamw tflink: so i was just asking what the likely status of fedup for final is 16:36
maxamillion nirik: is lorax the new pungi? 16:36
adamw as regards gui, 'smooth' operation, progress reporting 16:36
adamw maxam: they're both involved. 16:36
tflink it's getting better but I'm a bit behind on my fedup testing ATM 16:36
maxamillion adamw: rgtr 16:36
maxamillion rgr* 16:36
tflink my understanding is that there are some fixes in the pipeline that should help a few of the pain points 16:37
maxamillion the whole shim madness is something I barely understand 16:37
jreznik wwoods: are you around? 16:37
adamw maxam: i can forward you a gigantic email explanation of it i wrote if you like. 16:37
adamw #info some fixes for the rough edges of fedup impending 16:37
adamw okay, let's move on, time's a tickin 16:37
adamw #topic enterprise storage for F18/F19 16:37
wwoods I'm around! I'm also about. 16:37
adamw Viking-Ice: around? 16:37
Viking-Ice yup 16:37
adamw wwoods: too late! 16:37
adamw so this was yours... 16:38
wwoods Well then I'm outside. 16:38
Viking-Ice yup 16:38
wwoods and other prepositions. 16:38
mjg59 (Crying) 16:38
adamw and, indeed, positions. 16:38
j_dulaney adamw: I'd like the shim email as well 16:38
j_dulaney If you don't mind 16:38
Viking-Ice https://www.redhat.com/archives/anaconda-devel-list/2012-December/msg00025.html 16:38
adamw mjg59: was that email I CCed you on too outrageously inaccurate or anything? before i send it to anyone else 16:38
jreznik wwoods: (about dialog) - seems like there's another topic but if you have anything for fedup status - just fire it :) 16:39
mjg59 adamw: No, it seemed reasonable 16:40
adamw Viking-Ice: what was the outcome of that? iirc, 'advanced' storage types that require interaction to enable aren't going to work in F18 16:40
Viking-Ice basically there is no UI on newUI for Enterprise/Advantage storage so enterprise admins/users will have to rely ks only 16:40
adamw mjg59: cool. 16:40
adamw #info enterprise/advanced storage types that require interaction to enable/use will not work via UI in in F18, but can be used via kickstart. UI is scheduled to re-appear in F19 16:40
Viking-Ice this ofcourse is something that needs to be mentioned in the release notes 16:41
j_dulaney +1 16:41
adamw agreed 16:41
Viking-Ice not sure if there is specific Anaconda/Installer section in the release notes 16:41
adamw do you want a #action to let the docs team know about it? 16:42
adamw or i can take it if you like 16:42
Viking-Ice no I'll handle it 16:42
adamw ok 16:42
adamw #action viking-ice to let docs team know about advanced storage for release notes 16:42
adamw anything else to cover on this or shall we move on to criteria/test cases? 16:42
* jreznik will recheck RN notes for it 16:42
adamw #topic Test case / criteria revision 16:45
adamw so i think my proposal on the RPM package error criterion was positively received, i'll go ahead and put that into production 16:45
adamw #action adamw to put packaging error criterion revision into production 16:45
j_dulaney +1 16:46
adamw kparal's kickstart revision proposal spawned a big discussion which was interesting but might have stranded the proposal a bit 16:46
adamw any ideas for action there? try and reset the discussion to a list of ks parameters it's plausible to 'support' for f18? 16:46
kparal I think we should vote in F18 according to our best conscience and target this new criterion to F19 16:47
j_dulaney Aye, that would be a good move 16:47
kparal it will be a long discussion yet, I think 16:47
j_dulaney Actually, I really think that criterion revisions should not take effect until the *next* release 16:48
tflink ideally, yes 16:48
adamw viking's said the same thing 16:48
j_dulaney That's been my problem with all the criterion changes in the middle of this release 16:48
adamw i don't disagree in theory, but for f18, we've kinda had to rejig things on the run or else we'd have nothing applicable 16:48
jreznik adamw: +1 16:49
adamw #action kparal to try and 'reset' kickstart criterion discussion back to the proposed set of 'supported' commands 16:49
kparal hmm 16:49
Viking-Ice can we actually do that 16:49
adamw that okay? 16:49
kparal I can try 16:49
adamw Viking-Ice: sorry, actually do what? 16:50
Viking-Ice dont we just need to say all ks command have to work and test for those 16:50
tflink I'm not sure that's practical for F18 16:50
Viking-Ice why try to split it up? ( should be easy to test as well ) 16:50
adamw well the worry is that if we say that we'll find a bunch of fairly obscure bugs and then what? 16:50
adamw but i suppose we could do it that way around...test it and see how bad it is 16:50
Viking-Ice let anaconda deal with it 16:50
j_dulaney Heh 16:50
Viking-Ice it's their brokenness right 16:50
kparal adamw: well we can always waive some obscure problems, same as for graphics cards etc 16:51
j_dulaney Aye 16:51
adamw kparal: well we can do that because they're 'conditional' breakages 16:51
kparal but it becomes more tricky than with a defined set 16:51
adamw we don't have a criterion that says 'all graphics cards have to work' 16:51
j_dulaney "All KS commands should work unless they are really freaking off the wall" 16:51
adamw if we did, it'd be kinda hard to waive some graphics cards being broken :) 16:51
Viking-Ice unless they have spesific ks command that can never break or become backwards incompatible I cant see how we can 16:51
adamw so if we have a criterion that says 'all kickstart commands have to work', it seems quite hard for us to say 'well except THIS one, obviously!' 16:51
Viking-Ice so basically we should follow their list ( if exist ) or check for all existing supporting ks commands right? 16:52
adamw Viking-Ice: that was matt miller's idea, and it seems reasonable, but the problem is right now the documentation of kickstart commands is somewhat outdated and doesn't in any way define a 'core set' 16:52
kparal that goes back to my long-term complain about criteria being all-or-nothing game 16:52
adamw so for f18, it's a bit hard 16:52
adamw sigh, we seem to keep winding up on tangents here 16:52
kparal I'll try to restart the discussion 16:53
adamw the task is really just 'quantify the level of kickstart functionality we consider minimal for f18 final release', that does not seem like it should be impossible 16:53
kparal with just a core set of commands for F18 16:53
kparal and possible changes for F19 16:53
adamw and shouldn't require fundamental reimaginings of process or anything 16:53
Viking-Ice yes I just fail to see why the need to quantify it in the first place 16:53
adamw what's your alternative for dealing with whether breakages in kickstart should block f18 final? 16:54
adamw just do it case-by-case? 16:54
adamw i mean, we could do that. 16:54
adamw we could just say 'we don't want to fiddle with the criteria temporarily, so we'll just handle these one by one for now.' 16:54
Viking-Ice I would say it blocks always and questionable items dealt with on case by case bases 16:54
jreznik case by case could work for F18, especially as we do not know in what state it is... 16:54
adamw shall we go with that, then? seems straightforward 16:55
tflink it'll work, I suppose and will probably generate less discussion in the short term 16:56
tflink may lead to some interesting discussions about what is worth blocking for, though :) 16:56
kparal case by case is the best way, it just requires more time to discuss 16:56
adamw okay. well let's hope we don't get too many cases. :) 16:56
adamw #undo 16:57
zodbot Removing item from minutes: <MeetBot.items.Action object at 0x1f3f3e10> 16:57
kparal adamw: should we follow up on that discussion for F19? 16:57
adamw #agreed instead of trying to write a 'temporary criterion' we'll deal with kickstart proposed blockers on a case-by-case basis for F18 final and try to come up with a longer-term criterion for F19+ 16:57
adamw I think so, yeah. 16:57
kparal ok 16:57
j_dulaney kparal That would be a good idea 16:57
adamw you want to do that now or keep it for post-release? 16:57
tflink we might want to tell the anaconda devs what we're doing, though 16:57
* j_dulaney needs to be off for his final final 16:57
adamw yeah, and follow up on test list 16:57
kparal adamw: I'll write a note there 16:58
j_dulaney See y'all later. 16:58
adamw #action kparal to follow up on test@ discussion to explain the plan, and let anaconda team know 16:58
adamw cya dulaney 16:58
adamw okey dokey 16:58
adamw pschindl: are you planning to work on the issues identified in your test case / criteria survey? 16:58
pschindl adamw: yes 16:59
adamw cool 17:00
pschindl I'd like to go through it this week 17:00
adamw did anyone have any worries / questions about pschindl's proposals that haven't been brought up in the thread? 17:00
adamw #info pschindl will work on his proposed final test case changes (see thread 'Final criteria/Test cases interconnection') 17:01
adamw #topic open floor 17:01
adamw anyone have anything that wasn't covered? 17:01
* satellit needed; a good anaconda tutorial lots of people having problems understanding how to install 17:03
adamw the docs team are working on updating the install guide for newUI. 17:03
tflink and people having trouble with patience, aparrently 17:03
satellit +1 17:04
adamw tflink: where are we doing the blocker review this week? 17:05
tflink bugzappers, I think unless someone has a better idea 17:05
* kparal +1 17:05
adamw okey dokey 17:05
adamw everyone to #fedora-bugzappers for some thrilling blocker review in two minutes 17:06
adamw or, you know, head for the yaks 17:06
* adamw sets fuse for two minutes 17:06
adamw it's a classical physics fuse this week! 17:06
Viking-Ice It should be done in QA or someother channel then bugzappers 17:06
kparal it should be done in #fedora-anythingelsethanbugzappers, right? 17:07
Viking-Ice I still say QA 17:07
kparal -1 17:08
adamw thanks folks 17:08
Viking-Ice but I accept #fedora-anythingelsethanbugzappers as well 17:08
adamw #endmeeting 17:08

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

Retrieved from "https://fedoraproject.org/w/index.php?title=QA/Meetings/20121210&oldid=321705"