[Pulp-dev] Pulp 3 tag

[Brian Bouterse]

+1 to Tanya's suggestion.

Also I have an action item to start a separate thread on how we can
plan-and-then-close all pulp2 bugs that we are not actively working on. I
wanted to mention it here to identify it as a possible resolution to this
issue since it was related. I'll send this today.

On Tue, Apr 2, 2019 at 7:54 AM Tatiana Tereshchenko <ttereshc at redhat.com>
wrote:

> In my opinion, it's a part of triage or grooming process.
> Triage leader (for issues) and a person who grooms the task should pay
> attention to the tags.
>
> Tanya
>
> On Tue, Apr 2, 2019 at 1:47 PM David Davis <daviddavis at redhat.com> wrote:
>
>> Looking in redmine at our current sprint, I see several issues that don’t
>> have Pulp 3 tag that should. Here are some:
>>
>> https://pulp.plan.io/issues/4587
>> <https://pulp.plan.io/issues/4587>https://pulp.plan.io/issues/4595
>> <https://pulp.plan.io/issues/4595>https://pulp.plan.io/issues/4577
>> <https://pulp.plan.io/issues/4577>https://pulp.plan.io/issues/4576
>> <https://pulp.plan.io/issues/4576>https://pulp.plan.io/issues/4545
>>
>> <https://pulp.plan.io/issues/4545>Talking with the QE team, it’s
>> difficult for them to get a feel for how much Pulp 2 vs Pulp 3 work there
>> is. I guess we could try to get better about tagging issues when we create
>> them?
>>
>> However, at least one issue is by someone outside the core Pulp team and
>> I am not sure community members will know to tag their issues w/ Pulp 3
>> tag. Are there any other alternatives to ensuring Pulp 3 issues get
>> properly tagged?
>>
>> David
>> _______________________________________________
>> Pulp-dev mailing list
>> Pulp-dev at redhat.com
>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>
> _______________________________________________
> Pulp-dev mailing list
> Pulp-dev at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20190402/377f8a0c/attachment.htm>