16:34:54 #startmeeting Fedora Release Engineering 16:34:54 Meeting started Mon Dec 9 16:34:54 2013 UTC. The chair is dgilmore. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:34:54 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:35:12 #topic init who is here? 16:35:19 morning. 16:35:31 * sharkcz is here 16:35:43 * Kick__ is here 16:35:51 * masta is here 16:36:01 howdy folks 16:36:36 welcome 16:37:46 lets see if tyll is here 16:38:37 ok put this meeting in calendar... thanks for the reminder 16:38:46 dgilmore: thanks for staying awake so late 16:39:14 masta: i woke up 5 minutes ago :) 16:39:27 and will be going back to bed after the meeting 16:39:35 good plan 16:39:44 ok ive pinged tyll 16:39:50 dwa: are you around? 16:40:02 #topic tickets 16:40:10 we have one ticket 16:40:14 https://fedorahosted.org/rel-eng/ticket/3761 16:40:32 #topic ticket https://fedorahosted.org/rel-eng/ticket/3761 16:41:10 so we actually signed the .treeinfo file as .treeinfo.signed in beta 16:41:44 fedup uses it to verify the tree 16:42:04 dwa: did you sign it for secondaries? 16:42:38 it does bring up a opportunity for someone to contribute 16:42:51 yep 16:43:24 it's a simply thing to enhance I would imagine, just adding a checksum or whatever to the image compose script (guessing) 16:43:25 #info having a script to run to sign all the checksums .treeinfo files etc would be a useful thing to have 16:43:32 we should close that fedup bug if it's fixed. ;) 16:43:54 I guess it's in 'MODIFIED' now 16:44:11 nirik: i think they will close it once f20 final is shipped 16:44:23 i missed that this ticket was in the releng trac 16:44:30 it predates the fedup bug 16:44:34 yeah. 16:45:27 so.... I'm still learning what script does what... would the creation of the trees be the pungify script? Implying that this easy-fix would be near the end of that... 16:45:47 so if anyone is looking for a way to contribute writing a script to sign the tree would be useful 16:46:09 masta: we only sign the tree when its declared gold 16:46:22 oh! 16:46:25 all the TC and RC trees are unsigned 16:46:35 until we decide one is what we are shipping 16:47:08 interesting. so the signing of the treeinfo could be a trigger for other activities even 16:48:05 staging the tree on the mirrors and making torrents maybe 16:48:30 that would require a lot of scripting 16:48:47 so, one option... 16:48:49 so this ticket is basically done 16:48:51 a ansible playbook 16:49:00 which could in fact do things on multiple machines... 16:49:13 nirik: maybe 16:49:15 sign this here, move there, etc. 16:50:26 with how we changed things for f20 we have simplified many aspects of the compose process 16:50:32 at least for primary 16:51:31 * nirik nods 16:51:33 yeah 16:52:15 so do we have a script or existing automation that sorta does a "declare gold" ? 16:52:54 masta: not really 16:53:00 hiya 16:53:12 hi dan408_ 16:53:27 #topic scheduling 16:54:07 masta: dwa: nirik: does the updates pushing scheduling work for you guys? 16:54:24 sure, fine with me. I'm happy to do them whenever. (or help others) 16:54:37 dgilmore: yes, and I've created for myself a calendar reminder 16:54:42 I can also do weekends/holidays if folks want, since I am usually around. 16:55:21 Red Hat has the shutdown coming up and it would be good to get updates out at least a few tims during that period. does anyone want to volunteer to do so during their time off? if not ill do some pushes 16:55:31 I can do them. 16:55:35 nirik: you're free to keep weekends, but that seems kinda unfair to you... ifyou want me to pickup a weekend or whatever (you go on vacation) just let me know 16:55:40 * nirik is going to be home, but taking it easy. ;) 16:55:51 nirik: cheers 16:56:11 masta: sure, if you want some just ping me. ;) 16:56:11 ill be travelling home during the shutdown 16:57:15 nirik: we should get the updates pushing rotation into fedocal 16:57:30 sure, we can. 16:57:45 a 'releng' calendar would be easy to add. 16:58:17 would be good to do i think 16:58:50 sure, I can add one. 16:58:52 if you guys ever need any help let me know 16:58:57 * masta agree on fedocal 16:59:01 great idea 16:59:49 not that its a scheduling thing, but when the TC/RC ticket is opened up if someone wanted to do the compose feel free to. just co-ordinate in #fedora-releng 17:00:34 but scheduling wise F20 is almost done, F21 is going to require a lot of extra hands 17:00:54 dgilmore: I've been show that process, but I'd like some hand-holding when doing my first compose for tc/rc 17:01:18 masta: sure 17:02:28 * nirik nods. 17:03:25 when are you going to push updates for accepted freeze exceptions? just before the tc/rc? 17:03:41 sharkcz: we do them when qa lists them in a ticket. 17:03:43 sharkcz: when qa files the request to 17:03:54 its generally as soon as they have the karma 17:03:59 https://fedorahosted.org/rel-eng/ticket/5767 17:04:04 (the f20 ticket) 17:04:41 i really want to do away with the bleed repo for RC composes 17:05:02 ok, seems kernel-3.11.10-301.fc20 is not on the list yet although it has enough karma 17:05:07 push everything stabled and have the compose mash the tree 17:05:31 sharkcz: sometimes qa needs prodding 17:06:26 lets move on 17:06:35 #topic wiki cleanup 17:06:52 #link http://fedoraproject.org/wiki/ReleaseEngineering 17:07:02 thats the releng landing page 17:07:09 ive cleaned it up a bit 17:07:44 but it needs more work, as does the sops and other bits of info in the wiki about releng 17:07:58 I'm supposed to write-up a page about (my experiences) new contributors to help with releng. 17:08:12 sharkcz: if you wanted to add some onfo on s390 would be good 17:08:40 Kick__: dwa: if you wanted to put some ppc info in it would be good 17:08:58 dgilmore: yep, it's on my still long todo list 17:09:37 sharkcz: long lists seem common 17:11:29 #topic new year 17:12:04 after shutdown we will need to sit down and look at the compose process and work to streamline things a lot more 17:12:19 and adjust for all the new products stuff... 17:12:24 yeah 17:12:59 without some major improvements in how we do things i suspect we will have about a 24 hour turn around time to do composes 17:13:50 I think product definition will mean each product will have its own kickstart 17:14:28 fedora-install-server.ks fedora-install-workstation.ks and fedora-install-cloud.ks to replace fedora-install-fedora.ks 17:14:28 they could yeah. 17:14:41 they will have to im sure 17:14:57 each product will neednan installer tree 17:15:16 even if the installer tree is not the primary deliverable for the product 17:15:38 cloud working group is going to want to have updates images 17:15:50 that has updates applied 17:16:14 we are going to have to work with Legal to make sure we deal with sources appropriately 17:16:32 there is going to be a lot to do 17:16:48 Ive not followed the workstation product closely 17:17:05 I need to reach out to them to see what they are looking at 17:17:27 yeah. also there may well still be something like spins... 17:17:32 (secondary products) 17:17:47 #task dgilmore to reach out to all working groups to get from them a list of deliverables 17:17:58 right 17:18:15 ive not gotten a good answer from anyone over where spins fit 17:18:52 after their prd's the groups are supposed to deliver a list of what changes are needed to make the things they want... so I expect we will see a lot more stuff in january 17:18:54 dgilmore: not only list of deliverables, but also list of sources, I'm worrying there will be different sources too (tags/repos in koji) 17:19:21 sharkcz: right, im fighting now to make sure that there is not that 17:19:31 I'd really like to avoid that too. 17:19:37 I really don't want the distro forking 17:19:49 * sharkcz agrees 17:20:53 nirik: problem with "after their prd's the groups are supposed to deliver a list of what changes are needed to make the things they want" is that most of them won't have any idea on what changes are needed at the releng layer 17:21:09 true. 17:22:17 so for now its business as usal but keeping an eye on things to make sure that everything stays sane 17:22:40 #topic secondary arches 17:22:47 time for status updates 17:22:52 #topic secondary arches - s390 17:23:04 sharkcz: since your active you can go first :) 17:23:25 how are things? anything you need? 17:23:28 all good :-) http://fedora.danny.cz/s390/rebuild/koji-compare-f20.txt is the comparison to primary 17:23:36 all signed for f20 17:24:07 cool 17:24:24 when do you think you will be done? 17:25:43 likely a week after primary goes GA, don't expect any surprises, but I'm on PTO till the end of year 17:26:15 okay 17:26:26 cool 17:26:37 I want to go thru the diffs against primary and see what could be built yet 17:26:55 and at some point declare it done 17:27:02 sharkcz: have you looked at or are you using koji-stalk? 17:27:24 I've looked, but not using it yet 17:28:08 okay, i really think you should 17:28:09 by the diffs I mean to fix packages curretly failing to build 17:28:14 right 17:28:39 sharkcz: anything else you want to bring up? 17:28:54 nope 17:28:59 cool 17:29:14 #topic secondary arches - ppc 17:29:30 dwa: Kick__: where are things at? 17:29:32 I believe dwa is sick today, so... 17:29:34 dwa is out sick today 17:29:43 okay 17:29:53 ppc has http://ppc.koji.fedoraproject.org/koji/serverstatus for a quick overview wrt. package signing/pushing/build progress. 17:30:23 We're currently testing GA-TC5.1, looking good so far. We hope to release on the same day as primary again 17:30:44 okay 17:31:20 Kick__: anything else you want to bring up? 17:31:54 not for this meeting, but I'd like to bring up koji-gc for one of the next meetings 17:32:02 Kick__: releasing the same day as PA sounds really nice. 17:32:15 Kick__: okay. it just needs to be setup 17:32:41 Kick__: the plan on how to do koji-gc has been laid out 17:32:48 its now up to you guys to implement 17:33:13 #topic secondary arches - arm 17:33:15 yes, I know that dwa has been running some tests with it and I need to follow up with him 17:33:41 so 32 bit arm updates have been pushed out fairly regullary 17:34:00 I think all arches need to do better about pushing updates 17:34:26 aarch64 is currently being brought up 17:34:36 yes, I try do them weekly for s390 17:34:39 with the focus on rawhide 17:34:59 so hopefully there will be a aarch64 f21 release 17:35:13 hopefully 17:35:34 hopefully hardware available for people as well 17:35:43 #topic open floor 17:35:57 does anyone have anything they want to bring up? 17:36:06 nada 17:36:39 nothing specific, I want to go over the fixes/patches for koji/koji-shadow I sent to buildsys list and see what needs merging 17:36:55 IIRC there is few of them 17:37:07 sharkcz: okay. I thought id puleled them all in 17:37:28 sharkcz: lets go over them in #fedora-releng tomorrow morning your time 17:38:16 dgilmore: ok, I might be unavailable for some times as my PTO starts tomorrow 17:38:52 sharkcz: oh okay. lets do it there now, il go back to bed after 17:39:16 if there is nothing else ill wrap in 5 17:39:59 #endmeeting