17:01:08 #startmeeting EPEL (2019-06-05) 17:01:08 Meeting started Wed Jun 5 17:01:08 2019 UTC. 17:01:08 This meeting is logged and archived in a public location. 17:01:08 The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:01:08 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:01:08 The meeting name has been set to 'epel_(2019-06-05)' 17:01:08 #meetingname epel 17:01:08 The meeting name has been set to 'epel' 17:01:08 #topic Chair and Introductions 17:01:08 #chair bstinson Evolution nirik smooge pgreco tdawson 17:01:08 Current chairs: Evolution bstinson nirik pgreco smooge tdawson 17:01:32 o/ 17:01:48 ok, I'm here 17:02:01 hello 17:02:16 this may be a no quorum meeting. 17:02:24 #topic nirik is on break this week 17:02:30 #topic Chair and Introductions 17:02:40 #info nirik is on break this week 17:03:07 smooge, next week will be complicated also, I think 17:03:09 #topic Agenda 17:03:09 #info EPEL Proposal: EPEL Master branch AKA Rawhide 17:03:09 #info EPEL-8 17:03:19 #info There will be NO meeting next week 17:04:21 several of us will be locked in an escape room with a skunk 17:05:01 ok I don't see tdawson or bstinson so I will just paste what I was going to have and we go to open floor 17:05:22 * bstinson is here, but barely 17:05:48 ok, we could just recap last week, and the mails after that 17:06:08 #topic EPEL Rawhide (take 2) 17:06:08 #info https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/FYOOSAJOTDNCE4RLF32ORFO6WL2M5WD5/ 17:06:08 #topic EPEL-8 17:06:08 #info grobisplitter is in production 17:06:08 #info working with mohan to get koji.stg and builders.stg into place 17:06:09 #info koji.stg knows about EPEL-8 and some builds have been attempted 17:06:11 #info next steps are staging git, bodhi, etc etc 17:06:13 #topic Open Floor 17:06:49 basically, no rawhide in the name, but same concept 17:06:53 then epel8 (as stable) 17:07:08 and branch out on point release (and archive) 17:07:09 ok so last week sgallagh said he would offer some changes which he did and the proposal did not burn like mine 17:07:20 I thought epel meeting was in a hour ... sorry I'm late 17:07:27 ' 17:07:51 ah f@#$@#$ 17:07:55 tdawson, he keeps changing it to keep us awake, I thought it was 18:00 utc ;) 17:07:56 tdawson, you are right 17:08:18 do you guys want me to stop it because I bet bstinson may be available then 17:08:21 sorry 17:08:42 I don't think 1 hour will change bstinson's life 17:08:51 I'm ok either way 17:09:14 well he might be eating lunch and having quiet time and in an hour will be like 'hey guys can't a guy eat a ham sandwich without people calling meetings?' 17:10:00 i'm watching enough to pay attention now :) 17:10:14 bstinson, sorry 17:10:51 i got off the phone with the bank and glanced at the clock and said its :01 I am late starting the call 17:11:03 ok so back to 17:11:09 #topic EPEL Rawhide (take 2) 17:11:39 I like the propsoal, I think it would be a good one, and I think we could probably implement it 17:12:34 I can put it up for a vote at the next meeting, but I am looking to create 2 git branches in stging this afternoon epel-8 and epel-master-8 17:13:23 smooge, epel-8-master instead? 17:13:29 sure. 17:13:36 just thinking about sorting 17:13:44 I should be consistent 17:13:50 Also it sounds odd when spoken aloud 17:13:57 * sgallagh arrives late 17:14:04 no you are 45 minutes early 17:14:06 or 47 mins early 17:14:25 I misread my clock and panic'd I missed the meeting beginning again 17:14:26 I arrived precisely when I meant to! 17:14:56 so yes epel-8-master 17:15:01 I know people weren't thrilled about epel-rawhide ... I didn't know -master was what we ended up with ... or is this just to get something started? 17:15:20 well I was looking at master branch 17:15:29 so went with that 17:15:35 it can be epel-8-wagontrain 17:15:47 it can be epel-8-bonanza 17:15:56 it can be epel-8-have-gun-will-travel 17:15:57 epel-8-youcandoyourmesshere 17:16:06 :) 17:16:28 i figured master was clearer to what rawhide is in the other branches 17:16:29 and for stable epel-8-dontyoudarescrewthisone 17:16:44 I suggested elsewhere that we should declare “bobrossing” to be the opposite of bikeshedding, because the great sage would have told us to just pick a color and make something beautiful. 17:17:19 so let us bob ross this.. anyone have a particular cloud they want to call it? 17:17:51 the concept for not using rawhide is the same for not using master (acording to the ML) 17:17:52 Now that I think about it ... -master is fine ... similar to fedora master ... I just didn't recall us saying that. 17:17:57 master==rawhide 17:19:42 OK, if we have to decide on this minutae before discussing the general plan... we should probably at least describe the problem we're solving. 17:19:59 In Fedora, "Rawhide" kind of makes sense with its "wild west" (aka, limited rules) implication 17:20:10 But that's probably NOT what we actually want EPEL "Rawhide" to be. 17:20:20 tdawson: did SL do anything fancy here? 17:20:21 actually updates-testing is getting used for that 17:20:23 And the name we choose should probably reflect that 17:20:23 they did similar versioning. 17:20:37 tdawson: can't recall what you/they called it though 17:20:48 fastbugs 17:21:01 ok, naming aside, the concept is clear 17:21:08 fastlane ? 17:21:12 So before we try to pick a name, let's make sure we agree on how we intend people to use it 17:21:32 (whether they actually do as we intend is secondary and insoluble, so ignore it for now) 17:21:50 so the 2 parts I am wanting to use it for are : People who want stuff a 'rural lifestyle' versus the HOA that EPEL is 17:22:11 smooge: Those terms may not be globally-accessible. 17:22:20 no they probably are not 17:22:50 People who want to be able to put things which do not fit into what is 'extra' stable in regular EPEL. 17:23:19 This is what you *want* it to be, or what you expect it will be used for? 17:23:19 When RHEL does a major API update a place to stage the builds before they hit regular EPEL 17:23:30 Because those are different questions. 17:23:35 sgallagh, well I am seeing epel-testing being used for it already 17:24:05 smooge: That didn't answer the question :) 17:24:15 Is that what we *want*? 17:24:15 I want those out of epel-testing 17:24:18 I'd say no. 17:24:30 I'd say that realistically we want them to use modules to solve that particular problem 17:25:00 My perspective is that we want "rawhide" for "things that are being staged for an upcoming minor release" 17:25:26 sgallagh, or for a rebase 17:25:30 but yes 17:25:32 in that case I would definitely not call it rawhide or anything wild 17:25:40 just -future 17:25:51 pgreco: Well, we established that such rebases will be permitted only at a minor release 17:25:55 So same thing, really 17:26:05 ack 17:26:14 smooge: -future, -staging, -prototype 17:26:46 But again, let's first see if people agree with that use-case 17:28:42 On a short term basis ... I'm totally fine with calling it -master in stg while we figure out the final name. 17:29:05 actual I think -staging sounds good. 17:29:15 Yeah, that was the one I was leaning towards too 17:29:18 I can change the epel-rpm macros 17:29:25 Because it carries a strong implication that things shouldn't vary there forever 17:29:33 +1 on -staging 17:30:04 at least for now 17:30:13 ok will fix the epel-release in staging in the next build 17:30:55 ok anything else on this one? 17:31:09 I think any final vote on it should happen after next week 17:31:25 but we can do a -staging until we finish the EPEL-beta 17:32:15 workflow can be fedpkg build for epel-8 goes to epel-8-staging first it can then be tagged to epel-8-testing and then epel-8 17:32:20 Did we want to discuss the "dist tag on minor release" question? 17:32:45 no that has not been brought up at all 17:32:52 The question was raised about whether to abandon pending bodhi updates, but I thought it was unnecessary. 17:33:02 smooge: nirik asked about it on the email thread 17:33:11 in this meeting 17:33:16 sorry 17:33:44 Was I interpreting "ok anything else on this one?" too broadly? 17:34:07 sorry.. lets back up 17:34:21 that would be something to talk about and no one has brought it up at this meeting before 17:35:09 Sorry, I interpreted "this one" as teh "EPEL Rawhide" topic. 17:35:26 I thought you were asking for other items on that topic, so I raised one 17:35:29 so question one is 'dist tag on minor release' and how that would fit into epel-staging 17:35:40 and I agree that is a topic to be raised 17:36:08 we are in violent agreement I think 17:36:29 Please continue 17:39:18 and I got pinged and had to tell someone later.. sorry 17:39:37 ok so I think I just wanted to go over what we had on EPEL-8 currently 17:40:08 in fedora staging the koji has the bare minimums to know about RHEL-8 and default modules 17:41:20 the next steps are setting up the epel-release package with the right keys, get the signers to work, set up the branches and do test builds of packages to make sure things work 17:41:43 then it will be to set up any other items in staging which are part of the build train 17:42:23 bodhi, pdc, and probably some other items 17:43:08 then have people do builds in stg with fedpkg-stage following a usual work pattern 17:43:24 that should hopefully find all the skeletons in the closet 17:43:31 s/all/many of/ 17:44:21 currently I have us leaving beta by end of June and then we can start implementing all this in July in production 17:45:36 does that sound ok for everyone? I am hoping to hand it over for people to test builds etc around the 18th 17:46:07 Sounds good to me 17:46:31 I don't think I get a vote, but that sounds nice and soon :) 17:46:54 that sounds optimistic, but I like it 17:48:37 so a beta just means we get to build stuff and people could download things from koji.stg.fedoraproject.org. we don't have a staging downloader so composes I don't think will show up anywhere 17:49:06 the rest of stuff showing for realz would be in July 17:49:31 ok in that case I don't have anything else to say at the moment 17:49:48 #topic open floor 17:50:39 ok anything for the open floor? I think the minor distag and the bodhi-updates will need to be discussed at the next meeting when Kevin is here to articulate his wants 17:50:56 is there any concept around bootstrap/external repos? 17:51:20 I mean, many packages depend on the previous versions to build 17:52:25 so for things which depend on previous builds, I expect we will have to use F28 for anything to do that 17:52:42 that would be a good thing to test in builds as we will need to work out how that happens 17:53:25 that is what I was thinking (f28 or 29), but it needs a plan so we can tell people how to build those 17:53:26 I found that f28 works reasonably well for any side buildroots that you need to do a chain on 17:53:49 f29+ have newer pythons than what are in RHEL-8 17:54:28 so I am thinking we will have to chain from f28 even if the branch/sources you use is f30 17:55:00 Will there be a meeting next week or will it be in two weeks? 17:55:09 fwiw, for all the things I had to boostrap for centos8, I used f28 17:55:48 there will be no meeting next week 17:56:16 #info next meeting will be 2019-06-19 (hopefully at the right time) 17:57:15 #info for any bootstrapping of EPEL-8, using F28 will be recommended. 17:57:33 ok it is coming up to the hour.. and my headache medicine is calling 17:57:46 anything else for this week? 17:57:51 ok, meeting in 2 minutes :D 17:57:56 hahahaha 17:58:03 #endmeeting