[Pulp-dev] [pulp-internal] story backlog reduction

Michael Hrivnak mhrivnak at redhat.com
Mon Sep 12 15:48:51 UTC 2016

#48 continues to be valid. We should have a better way of storing secrets.
Planning and investigation would be required to produce a more concrete
proposal, but I don't think we need to close this.

I think the rest can be closed.

Thanks for pruning!

On Mon, Sep 12, 2016 at 11:44 AM, Austin Macdonald <amacdona at redhat.com>

> I have been closing more stories, and I would like some feedback for
> these 10. IMHO, these do not convey a clear idea, but might have more
> meaning to one of you and perhaps be expanded into a proper story.
> Please have a glance at these and let me know if there are any that
> should *not* be closed.
> https://pulp.plan.io/issues/46
> https://pulp.plan.io/issues/47
> https://pulp.plan.io/issues/48
> https://pulp.plan.io/issues/49
> https://pulp.plan.io/issues/50
> https://pulp.plan.io/issues/52
> https://pulp.plan.io/issues/53
> https://pulp.plan.io/issues/54
> https://pulp.plan.io/issues/58
> https://pulp.plan.io/issues/63
> _______________________________________________
> 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/20160912/7f972823/attachment.htm>

More information about the Pulp-dev mailing list