[Pulp-dev] Katello Pulp 3 priority tags

[David Davis]

It's across plugins. If plugin issues are tagged P1/P2 I don't think that
should block the 3.0 GA though unless there is some core work involved.

David


On Thu, Jun 27, 2019 at 4:05 AM Tatiana Tereshchenko <ttereshc at redhat.com>
wrote:

> Thanks for sharing.
> Are those flags used for the core only or plugins' issues will be tagged
> using those flags as well?
>
> Tanya
>
> On Wed, Jun 26, 2019 at 11:16 PM David Davis <daviddavis at redhat.com>
> wrote:
>
>> I wanted to notify everyone of how we're defining Katello's tags on the
>> Pulp 3 integration work so that we're all the same page. These are tags you
>> may see on issues in our redmine. Previously, Katello used four tags
>> (P1-P4) but we've narrowed this down to just three (P1-P3) which we've
>> defined as:
>>
>> P1 - Blocking Katello today. This is something that is actively blocking
>> the Katello integration effort. It needs to be addressed ASAP.
>> P2 - Not currently blocking Katello but will eventually will. It's likely
>> that these will transition to P1s if left unaddressed.
>> P3 - A nice to have. A convenience or improvement (e.g. speed) that
>> Katello would like.
>>
>> I think both the P1 and P2 items should block the 3.0 GA release of Pulp.
>> So please plan and prioritize the work accordingly. I've asked the Katello
>> developers to tag all issues with one of these tags when they open them in
>> our redmine.
>>
>> If you have any questions, let me know.
>>
>> David
>> _______________________________________________
>> 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/20190627/56e2ac2f/attachment.htm>