I forgot to mention that the original queries included the Debian plugin's
tickets, but after seeing their issues it was clear that I should not
adjust their state.
On Fri, Apr 12, 2019 at 4:53 PM Kersom wrote:
> Total per component.
>
> Crane 16
> Docker Support 52
> Nectar 17
> OSTree Support
After some discussion the proposal has been adjusted to leave publishers
as-is and only introduce Master/Detail Publications with this change.
https://pulp.plan.io/issues/4678#note-6
Please provide more feedback as this likely will be work we try to include
for rc2.
On Thu, Apr 11, 2019 at 4:20 P
Total per component.
Crane 16
Docker Support 52
Nectar 17
OSTree Support 11
Pulp 689
Puppet Support 41
Python Support 12
RPM Support 186
Total 1024
On Fri, Apr 12, 2019 at 4:33 PM Brian Bouterse wrote:
> As I'm sure you can see from the redmine notifications, the mass-closing
> happened. 1024 i
Pulp2 tag sounds great to me.
On Fri, Apr 12, 2019, 16:23 Brian Bouterse wrote:
> +1 to making a 'Pulp 2' tag
>
>
> On Fri, Apr 12, 2019 at 3:16 PM David Davis 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 Pul
+1 to making a 'Pulp 2' tag
On Fri, Apr 12, 2019 at 3:16 PM David Davis 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?
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 add
