@daviddavis, +1 to the next steps you propose. Thank you for doing all this.
On Wed, Apr 22, 2020 at 9:19 AM Tatiana Tereshchenko <ttere...@redhat.com> wrote: > Thanks for the suggested automation, it would keep us more organised > with issues belonging to the right projects! > > How do we close everything which is not in a changelog, do we associate it > with the same release milestone or leave it without any? > It seems that the majority are CI/CD and installer issues. Does it > make sense to have a separate process for them? Installer has its own > releases. I understand that some releases are tightly connected to the > pulpcore release, so maybe it can be closed when pulpocre is out. > With the installer being versioned with pulpcore, I'm in favor of keeping it as a tag in the pulpcore Redmine over having its own Redmine project. I don't have a strong opinion here, just sharing some potential concerns. > > Tanya > > On Wed, Apr 22, 2020 at 1:56 PM David Davis <davidda...@redhat.com> wrote: > >> Thanks for the response. I think the next steps for me will be: >> >> 1. Merge https://github.com/pulp/plugin_template/pull/209 >> 2. Add a step to the release guide to check/cleanup any MODIFIED issues >> >> I plan to proceed with these steps by April 24 if there is no other >> feedback. >> >> David >> >> >> On Tue, Apr 21, 2020 at 8:13 AM Ina Panova <ipan...@redhat.com> wrote: >> >>> Comments inline. >>> >>> >>> -------- >>> Regards, >>> >>> Ina Panova >>> Senior Software Engineer| Pulp| Red Hat Inc. >>> >>> "Do not go where the path may lead, >>> go instead where there is no path and leave a trail." >>> >>> >>> On Mon, Apr 20, 2020 at 2:41 PM David Davis <davidda...@redhat.com> >>> wrote: >>> >>>> During the pulpcore team meeting last week, we noted that after the >>>> latest pulpcore release there were a number of issues in redmine still at >>>> MODIFIED. I took an action item to go through them and they seem to fall >>>> into four categories: >>>> >>>> 1. Issues that got filed against pulpcore but were fixed in a plugin >>>> >>>> I think that item 1 is worth trying to fix by automation. The commit >>>> validation could check that the issue project for the attached issue >>>> matches the repo. I have a proof of concept here: >>>> >>>> https://github.com/pulp/plugin_template/pull/209 >>>> >>>> +1 >>> >>> 2. Issues without code changes (eg tasks, epics, etc) getting set to >>>> MODIFIED upon completion >>>> 3. Issues that got pulled/reverted before the release went out >>>> >>>> Optimally, we'd set these to CLOSED when they are completed. I think >>>> the release person could also check though. I'd propose we add a step to >>>> the release guide that asks the release person to clean up any items at >>>> MODIFIED after releasing. >>>> >>>> +1 to that, I had the same thought. >>> >>> 4. Issues against the installer and plugin_template. >>>> >>>> I would also make sure that they are in a closed state after the >>> release. >>> >>> Looking for feedback on what to do with these. >>>> >>>> David >>>> _______________________________________________ >>>> Pulp-dev mailing list >>>> Pulp-dev@redhat.com >>>> https://www.redhat.com/mailman/listinfo/pulp-dev >>>> >>> _______________________________________________ >> Pulp-dev mailing list >> Pulp-dev@redhat.com >> https://www.redhat.com/mailman/listinfo/pulp-dev >> > _______________________________________________ > Pulp-dev mailing list > Pulp-dev@redhat.com > https://www.redhat.com/mailman/listinfo/pulp-dev >
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev
