[Pulp-dev] Removing a few sprint items?
daviddavis at redhat.com
Thu Mar 15 13:30:31 UTC 2018
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.
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
> 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>
>> 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 
>> Create and publish an ansible role to install apache and configure it for
>> pulp  <--- note the code already support Apache and nginx
>> Distribute Pulp with Pulp 
>> Can others give input on this decision?
>> : https://pulp.plan.io/issues/2988
>> : https://pulp.plan.io/issues/2921
>> : https://pulp.plan.io/issues/2325
>> Thank you!
>> Pulp-dev mailing list
>> Pulp-dev at redhat.com
> Pulp-dev mailing list
> Pulp-dev at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pulp-dev