15:31:36 <fao89> #startmeeting Pulp Triage 2019-12-10
15:31:36 <fao89> !start
15:31:36 <fao89> #info fao89 has joined triage
15:31:37 <pulpbot> Meeting started Tue Dec 10 15:31:36 2019 UTC.  The chair is fao89. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:31:37 <pulpbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
15:31:37 <pulpbot> The meeting name has been set to 'pulp_triage_2019-12-10'
15:31:37 <pulpbot> fao89: fao89 has joined triage
15:31:45 <dkliban> #info dkliban has joined triage
15:31:45 <dkliban> !here
15:31:45 <pulpbot> dkliban: dkliban has joined triage
15:31:49 <fao89> !next
15:31:50 <pulpbot> fao89: No issues to triage.
15:31:58 <dkliban> oh
15:31:58 <ppicka> #info ppicka has joined triage
15:31:58 <ppicka> !here
15:31:58 <pulpbot> ppicka: ppicka has joined triage
15:31:59 <fao89> Open floor!
15:33:15 <ttereshc> #info ttereshc has joined triage
15:33:15 <ttereshc> !here
15:33:15 <pulpbot> ttereshc: ttereshc has joined triage
15:35:46 <bmbouter> #info bmbouter has joined triage
15:35:46 <bmbouter> !here
15:35:46 <pulpbot> bmbouter: bmbouter has joined triage
15:35:49 <daviddavis> #info daviddavis has joined triage
15:35:49 <daviddavis> !here
15:35:49 <pulpbot> daviddavis: daviddavis has joined triage
15:36:11 <daviddavis> I think there are some unassigned issues for 3.0
15:36:14 <daviddavis> let me check
15:36:31 <daviddavis> https://pulp.plan.io/issues?query_id=77
15:36:48 <daviddavis> there are two. I think these need to be completed today right?
15:37:04 <bmbouter> yes
15:37:22 <bmbouter> I'm taking 5661 assigned now
15:37:40 <daviddavis> bmbouter: did you see dalley's comment? https://pulp.plan.io/issues/5661#note-5
15:38:18 <bmbouter> I did but I'm not prepared to facilitate a PUP
15:38:34 <bmbouter> I also believe the PUP process to be defunct completely
15:38:44 <daviddavis> ha ok
15:39:13 <bmbouter> I agree w/ his point about process and PUPS are intended to be a process place
15:39:40 <bmbouter> it's very unclear on what voting means with PUPs these days
15:40:10 <daviddavis> where do you see mention of PUPs? I only see the wiki mentioned
15:41:04 <dalley> I think one of my original edits mentioned pups
15:41:11 <daviddavis> oh
15:42:06 <bmbouter> yes this comment was edited
15:42:10 <bmbouter> the original was "I actually think the appropriate place for this is a PUP, since it's a process discussion. Putting it directly in the docs doesn't appeal to me because It's not something that contributors need to be terribly concerned with, as they won't necessarily be following our guidelines for their own plugins, and we'll be doing releases for our own plugins."
15:42:30 * bmbouter checking he isn't crazy lol
15:42:33 <daviddavis> hehe
15:42:44 <daviddavis> I think the wiki is a good suggestion but I don't have a strong preference
15:43:00 <bmbouter> I'm +1 to wiki or to docs
15:43:18 <bmbouter> we can keep on wiki for now if you all want I'm ok w/ that
15:43:24 <daviddavis> +1
15:43:32 <bmbouter> and I can just try to improve the wiki page here today then:  I actually think the appropriate place for this is a PUP, since it's a process discussion. Putting it directly in the docs doesn't appeal to me because It's not something that contributors need to be terribly concerned with, as they won't necessarily be following our guidelines for their own plugins, and we'll be doing releases for our own
15:43:34 <bmbouter> plugins.
15:43:38 <bmbouter> wrong paste...
15:43:42 <bmbouter> https://pulp.plan.io/projects/pulp/wiki/Pulp3_Release_Guide
15:43:56 <daviddavis> great, sounds good
15:44:19 <bmbouter> what to do w/ the "plugin parts" this page would become about pulpcore and pulp_file
15:44:37 <bmbouter> make a separate page for Pulp3 Plugin Release Guide?
15:44:45 <bmbouter> keep it on one page and leave the plugin parts alone?
15:45:36 <daviddavis> I think we can just document pulp_file and if plugins have a different release process, they can document it themselves
15:45:45 <bmbouter> that'll work
15:45:51 <ttereshc> yeah +1
15:45:51 <bmbouter> I'll do that as part of my ticket I just took as assigned
15:45:57 <daviddavis> great
15:46:20 <bmbouter> FYI dev freeze for 3.0 items happens ~ 6 hours!
15:46:43 <bmbouter> cherry picking starts tomorrow morning Eastern time then the build
15:46:48 * daviddavis screams in terror
15:46:59 * bmbouter runs away
15:47:21 <ttereshc> rpm folks, we have one doc task  https://pulp.plan.io/issues/5759 to complete before ga
15:47:39 <daviddavis> I think 5563 is probably best handled when we generate the new changelog
15:47:44 <daviddavis> https://pulp.plan.io/issues/5563
15:48:09 <daviddavis> I can open a PR to mark exporters as tech preview in the api
15:51:21 <bmbouter> daviddavis: and also will some notes be added to the docs like ..warning statements?
15:51:34 <bmbouter> also we'll include these in the release announcement I plan to write tomorrow
15:51:39 <bmbouter> so they'll be in that either way
15:51:52 <daviddavis> bmbouter: which docs?
15:51:55 <bmbouter> and the changelog I'll put it there too (like you're saying)
15:52:46 <bmbouter> I thin only the S3 page https://docs.pulpproject.org/en/3.0/nightly/installation/storage.html#amazon-s3
15:52:57 <daviddavis> +1
15:53:03 <bmbouter> also here on this setting  https://docs.pulpproject.org/en/3.0/nightly/settings.html#profile-stages-api
15:53:26 <daviddavis> ok cool
15:53:29 <bmbouter> and probably a stdout or stderr on this command so it shows when run https://github.com/pulp/pulpcore/blob/master/pulpcore/app/management/commands/stage-profile-summary.py
15:53:43 <bmbouter> probably here https://github.com/pulp/pulpcore/blob/master/pulpcore/app/management/commands/stage-profile-summary.py
15:53:57 <daviddavis> I'm a bit hesitant to make all these changes
15:54:03 <daviddavis> I'm worried about forgetting about them
15:54:23 <daviddavis> I personally feel like the release announcement and changelog should suffice. maybe docs.
15:54:24 <bmbouter> if we don't then a user could claim they didn't know
15:55:00 <bmbouter> well that's what I imagined, however far (or not far) you want to take that is ok w/ me
15:55:26 <bmbouter> the thinking is when users reach for the tool they should experience the "hey this is not fully supported" when they go to use it
15:55:34 <bmbouter> to avoid heartache on both sides later
15:55:44 <bmbouter> s/heartache/headache/
15:55:49 <daviddavis> part of my concern is that I already have 3 tasks to work on today
15:55:59 <daviddavis> maybe someone else can do 5563
15:56:05 <bmbouter> yes maybe someone can
15:57:11 * bmbouter listens
15:58:26 <bmbouter> I'd rather do it fully and delay than to do it light and deliver
16:01:45 <daviddavis> bmbouter: would you have time to open a PR for the cli parts? I can update the docs/api and review your PR
16:01:59 <bmbouter> I can tomorrow
16:02:05 <bmbouter> if it's you and me it's going to be a delay
16:02:15 <bmbouter> and that's fine
16:02:25 <daviddavis> ok, yea I also don't know who will review my docs changes this afternoon
16:02:25 <bmbouter> so I'll plan to pick up whatever isn't done tomorrow on that one
16:02:32 <daviddavis> ok
16:02:42 <bmbouter> dkliban: ^?
16:02:45 <bmbouter> for review
16:03:22 <dkliban> bmbouter: are you asking if i can review work?
16:03:48 <daviddavis> yes, specifically docs changes
16:05:16 <dkliban> yes, i can help with reviews
16:05:30 <x9c4> dkliban++
16:05:30 <pulpbot> x9c4: dkliban's karma is now 401
16:05:34 <daviddavis> cool, I will send you some PRs
16:05:41 <x9c4> reviewer of the day...
16:07:59 <fao89> #endmeeting
16:07:59 <fao89> !end