15:31:54 #startmeeting 15:31:54 Meeting started Mon Apr 21 15:31:54 2014 UTC. The chair is dgilmore. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:31:54 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:32:00 #meetingname releng 15:32:00 The meeting name has been set to 'releng' 15:32:07 ahoyhoy 15:32:07 #topic roll call 15:32:39 #chair dwa sharkcz masta tyll bochecha 15:32:39 Current chairs: bochecha dgilmore dwa masta sharkcz tyll 15:32:47 * bochecha is here 15:32:51 #chair nirik 15:32:51 Current chairs: bochecha dgilmore dwa masta nirik sharkcz tyll 15:33:25 * masta is here 15:33:56 nirik said he has an appointment for his dogs 15:34:01 lets get started 15:34:08 #topic tickets 15:34:25 #link https://fedorahosted.org/rel-eng/report/10 15:34:45 #topic https://fedorahosted.org/rel-eng/ticket/5854 15:34:52 masta: get a chance? 15:35:32 no I still have not. =( 15:36:12 okay 15:36:25 #topic https://fedorahosted.org/rel-eng/ticket/5362 15:36:46 I have not yet got xz repodata implemented 15:37:08 I dont know that we really need to keep the meeting keyword on these two tickets 15:37:22 #topic https://fedorahosted.org/rel-eng/ticket/5870 15:37:28 rawhide signing 15:37:44 not really sure we have anything much to discuss here 15:38:08 we know tthat sigul will need a lot of work to be able to do it 15:38:42 is there any place where that needed work is detailed? 15:39:53 bochecha: not that I know of 15:40:03 it flies against how sigul was designed 15:40:26 sigul does not have a roadmap or active development 15:40:35 :-/ 15:41:11 a lot of the tools we use don't have roadmaps 15:42:14 well that is depressing to read. 15:42:56 it is what it is 15:43:06 lets move on 15:43:11 #topic secondary arches 15:43:19 #topic secondary arches - ppc 15:43:28 dwa: want to give us a status update 15:43:56 sure 15:44:09 ppc64 is generally chugging along, nothing interesting to report 15:44:43 ppc64le has a temporary koji hub up to allow IBM to contribute and we've built/noarch imported a whole lot of builds 15:44:54 but still with some bootstrap hacks present 15:45:38 next steps we're taking are targetting some specific package sets to make sure we've got everything e.g. for a base install 15:45:52 then we take out the hacks and see what breaks when we try to rebuild stuff :) 15:46:15 ppc64le koji is at http://ppc-le.koji.fedoraproject.org/koji, normal fedora certs work for building stuff etc. 15:46:58 on a general note we're aware of the mass rebuild coming up and ppc64 will be ready for it. (doubt ppc64le will be) 15:47:42 that's about it 15:48:03 okay, not entirely sure when exactly the mass rebuild will be 15:48:31 I think the releng ticket about it had a target date in it 15:48:42 it doesnt 15:48:48 we need to work out everything needed 15:48:54 and work out a date 15:49:15 "Branching is no earlier than 2014-07-08, so mass rebuild should be done by 2014-06-09 (with 4 weeks cleanup grace period)." 15:49:28 that's what we were keeping in mind, anyways 15:49:34 schedule is stil up in teh air a bit 15:49:53 mass rebuild likely will start in early may 15:50:13 but we need to check that everything that shold land before it lands 15:50:36 #topic secondary arches - aarch64 15:50:36 nod. rawhide on ppc64 was generally caught up last I checked, so I'm not terribly worried 15:50:54 aarch64 is getting closer and closer to rawhide 15:51:05 still some porting needed 15:51:17 kinda funny we are bringing up two new arches right now 15:51:37 'funny' 15:52:02 I do need to find out where the aarch64 boxes my boss ordered are and when they will get to phx 15:53:03 we also need to look at making sure all the compose tools work and we produce useable media 15:53:19 #topic secondary arches - s390 15:53:31 sharkcz seems to be not around 15:53:37 yeah. IBM guys were getting antsy to see something happen with the ppc64le patches they sent a while back 15:53:39 but I am not aware of anything 15:53:41 yeah funny, maybe MIPS will be brought back again too 15:53:42 holiday in CZ today, I do believe 15:54:01 like the sane parts of the work they get easter monday off 15:54:03 :) 15:54:08 (heck, it's technically a state holiday today in Mass too... *company* holiday in CZ though) 15:54:29 australia has a 4 day weekend for easter 15:54:37 so does HK 15:54:53 most of the world does 15:55:14 the US is silly when it comes to national holidays 15:55:20 anyway 15:55:25 #topic open floor 15:55:36 anyone have anything they want to discuss? 15:56:07 just a quick note I think I may start working on hacking in rpm verification to koji-shadow for noarch imports 15:56:08 I have a quick question first: how does one add a ticket to the agenda of the meeting? 'meeting' keyword? 15:56:09 who has push duty? 15:56:13 since that's been annoying on ppc64 lately 15:56:24 dwa: add meeting to the keywords 15:56:41 masta: I can never keep track... I just get vauge feelings it's my turn every 2-3 weeks and wait for someone to yell at me ;) 15:56:50 masta: i believe its dwa this week 15:56:56 see? :) 15:56:56 since you were last week 15:57:12 dgilmore: ok, so I should probably add it to the lookaside hash ticket then :) 15:57:28 bochecha: probably 15:57:29 anybody had any comment about my last email to the list? 15:57:39 bochecha: not yet seen it 15:57:58 oh hey, push duty is on the releng calendar now 15:57:59 https://lists.fedoraproject.org/pipermail/rel-eng/2014-April/017654.html 15:58:08 (just so it's in the minutes) 16:00:03 gah, fedocal doesn't play nice with gmail :( 16:00:09 s/gmail/gcalendar 16:00:31 dwa: :( 16:01:03 I wanted to bring up roadmaps for the things we are responsible for 16:01:24 I think we should sit down and work out what things we ant to do with the tools 16:01:32 and be a little more active in developing them 16:01:44 sounds good 16:01:55 +1 16:02:51 overall need to document better the things that need worked on 16:03:07 and set more open goals and task 16:03:09 s 16:04:18 probably its something I need to do most of all 16:04:38 but feel free to come up with things that need doing 16:04:48 or would be good to do 16:05:09 in the near future porting everything to python3 will be big 16:05:54 anyone have anything else? 16:06:08 or should we wrap up? 16:06:15 I'm good 16:06:36 okay 16:06:47 going in 3 16:06:48 2 16:06:48 1 16:06:51 #endmeeting