[Pulp-dev] Removing a few sprint items?

[Brian Bouterse]

Thank you both for the feedback. I share the concern that we may run out of
NEW items. I added a monday meeting agenda item for us to check-in on if
additional work needs to be added then. I'm wanting to defer adding more
today with the hope that sprint 34 will get to 100% modified and will have
nothing to carry forward.

With no -1's, let's, I'll remove those three. If others find this note
after it's been done and want to change it, please bring this back up.
Consensus on mailing lists is hard. :)

On Thu, Mar 15, 2018 at 9:30 AM, David Davis <daviddavis at redhat.com> wrote:

> I just want to point out that we only have 4 NEW non-plugin issues on the
> sprint and 2 weeks left. If we remove these three issues, then we’ll only
> have 2 pulpcore issues left.
>
> I’m not opposed to removing these issues but we should maybe consider
> adding a few.
>
>
> David
>
> On Thu, Mar 15, 2018 at 7:19 AM, Ina Panova <ipanova at redhat.com> wrote:
>
>> #2988 was automatically moved to srpint 34 because it was in assigned
>> state and the assignee was not present on the planning so we moved it
>> forward and let the decision up to the assignee whether to continue to work
>> on this or drop form the sprint.
>> Since you're just unassigned it i think we can drop this issue from the
>> sprint.
>>
>>
>>
>>
>> --------
>> 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 Wed, Mar 14, 2018 at 5:03 PM, Brian Bouterse <bbouters at redhat.com>
>> wrote:
>>
>>> I didn't get a chance until now to look at the sprint 34 items in a
>>> detailed way. I want us to consider removing three of them from the sprint.
>>> The reasoning is that these areas of work are not part of the pulp3 core
>>> beta deliverables.
>>>
>>> Exception when raising a user-Defined Exception that has a custom
>>> __init__ signature [0]
>>>
>>> Create and publish an ansible role to install apache and configure it
>>> for pulp [1]  <--- note the code already support Apache and nginx
>>>
>>> Distribute Pulp with Pulp [2]
>>>
>>> Can others give input on this decision?
>>>
>>> [0]: https://pulp.plan.io/issues/2988
>>> [1]: https://pulp.plan.io/issues/2921
>>> [2]: https://pulp.plan.io/issues/2325
>>>
>>> Thank you!
>>> Brian
>>>
>>> _______________________________________________
>>> 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/20180315/85b7a249/attachment.htm>