[Pulp-dev] Pulp 3 tag

Tue Apr 16 10:24:21 UTC 2019

Curiosity question - what we will benefit from removing tags Pulp 3, Pulp 3
MVP, and Pulp 3 RC Blocker?
Except of tons notifications received? I would keep them on the issues as
they are, for historical reasons of pulp3 development.

--------
Regards,

Ina Panova
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 15, 2019 at 10:18 PM David Davis <daviddavis at redhat.com> wrote:

> The Pulp 2 tag has been created in redmine. Please start using it to tag
> issues that apply to Pulp 2. We’re also applying the new Pulp 2 tag to
> issues without the Pulp 3 tag in the following projects in redmine:
>
> Debian
> Crane
> Docker
> Nectar
> OSTree
> Packaging
> Pulp
> Puppet
> Python
> RPM
>
> This includes about 1161 issues. Please let us know if there are any
> issues that shouldn’t be tagged or ones we have missed.
>
> The final step which we hope to do on Wednesday will be to remove the
> tags: Pulp 3, Pulp 3 MVP, and Pulp 3 RC Blocker. We’ll make csv backups for
> each before we remove them.
>
> David
>
>
> On Mon, Apr 15, 2019 at 2:52 PM Mike DePaulo <mikedep333 at redhat.com>
> wrote:
>
>> +1 to the "Pulp 2" tag.
>> (I was just thinking this.)
>>
>> On Fri, Apr 12, 2019 at 4:28 PM Austin Macdonald <amacdona at redhat.com>
>> wrote:
>>
>>> Pulp2 tag sounds great to me.
>>>
>>> On Fri, Apr 12, 2019, 16:23 Brian Bouterse <bbouters at redhat.com> wrote:
>>>
>>>> +1 to making a 'Pulp 2' tag
>>>>
>>>>
>>>> On Fri, Apr 12, 2019 at 3:16 PM David Davis <daviddavis at redhat.com>
>>>> wrote:
>>>>
>>>>> I’ve been thinking through this and I think there are 3 steps to
>>>>> perform:
>>>>>
>>>>> 1. Create a Pulp 2 tag
>>>>> 2. Assign the Pulp 2 tag to issues not tagged with Pulp 3
>>>>> 3. Remove the Pulp 3 tag
>>>>>
>>>>> Does that make sense? If so, I’d like to perform 1 and create the Pulp
>>>>> 2 tag in the next few days so we can start adding it to issues.
>>>>>
>>>>> I’ll follow up with more concrete plans for steps 2 and 3 next week.
>>>>>
>>>>> David
>>>>>
>>>>>
>>>>> On Thu, Apr 11, 2019 at 11:10 AM David Davis <daviddavis at redhat.com>
>>>>> wrote:
>>>>>
>>>>>> Cool, I will try to think through how to transition and we can
>>>>>> discuss at the team meeting Monday.
>>>>>>
>>>>>> David
>>>>>>
>>>>>>
>>>>>> On Thu, Apr 11, 2019 at 11:04 AM Ina Panova <ipanova at redhat.com>
>>>>>> wrote:
>>>>>>
>>>>>>> +1 to create a pulp2 tag after mass-close
>>>>>>>
>>>>>>>
>>>>>>> --------
>>>>>>> Regards,
>>>>>>>
>>>>>>> Ina Panova
>>>>>>> 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 Thu, Apr 11, 2019 at 3:48 PM Brian Bouterse <bbouters at redhat.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Great idea David!
>>>>>>>>
>>>>>>>> Once we get through tomorrow's mass-close, let's plan a transition
>>>>>>>> to remove the Pulp3 tag and introduce a Pulp 2 tag instead.
>>>>>>>>
>>>>>>>> On Thu, Apr 11, 2019 at 9:34 AM Dana Walker <dawalker at redhat.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> +1
>>>>>>>>>
>>>>>>>>> Dana Walker
>>>>>>>>>
>>>>>>>>> Software Engineer
>>>>>>>>>
>>>>>>>>> Red Hat
>>>>>>>>>
>>>>>>>>> <https://www.redhat.com>
>>>>>>>>>
>>>>>>>>> <https://red.ht/sig>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Thu, Apr 11, 2019 at 9:22 AM Daniel Alley <dalley at redhat.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> I feel like using the Pulp 3 tag is suboptimal since we are
>>>>>>>>>>> closing out most of our Pulp 2 issues and a majority of the new
>>>>>>>>>>> bugs/tasks/stories are for Pulp 3. Wouldn’t it make more sense to create a
>>>>>>>>>>> Pulp 2 tag and use it on the rare Pulp 2 issues that get filed?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Agreed, +1 to having a "Pulp 2" tag to replace the Pulp 3 tag.
>>>>>>>>>>
>>>>>>>>>> On Thu, Apr 11, 2019 at 9:19 AM David Davis <
>>>>>>>>>> daviddavis at redhat.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> I feel like using the Pulp 3 tag is suboptimal since we are
>>>>>>>>>>> closing out most of our Pulp 2 issues and a majority of the new
>>>>>>>>>>> bugs/tasks/stories are for Pulp 3. Wouldn’t it make more sense to create a
>>>>>>>>>>> Pulp 2 tag and use it on the rare Pulp 2 issues that get filed?
>>>>>>>>>>>
>>>>>>>>>>> David
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Thu, Apr 11, 2019 at 8:27 AM Ina Panova <ipanova at redhat.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> +1 to handle tag during the triage process
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --------
>>>>>>>>>>>> Regards,
>>>>>>>>>>>>
>>>>>>>>>>>> Ina Panova
>>>>>>>>>>>> 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 Tue, Apr 2, 2019 at 3:53 PM Brian Bouterse <
>>>>>>>>>>>> bbouters at redhat.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> +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
>>>>>>>>>>>>>>
>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>> 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
>>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> 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
>>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> 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
>>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> 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
>>>>
>>> _______________________________________________
>>> 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
>>
> _______________________________________________
> 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/20190416/4aa6305e/attachment.htm>