[Pulp-dev] MODIFIED issues
daviddavis at redhat.com
Wed Apr 22 11:53:48 UTC 2020
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
On Tue, Apr 21, 2020 at 8:13 AM Ina Panova <ipanova at redhat.com> wrote:
> Comments inline.
> 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 <daviddavis at 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:
> 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.
>> Pulp-dev mailing list
>> Pulp-dev at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pulp-dev