+1 to what Robin said. Barring any other feedback now, we can create a new issue when needed and just close this one.
Dana Walker Associate Software Engineer Red Hat <https://www.redhat.com> <https://red.ht/sig> On Fri, Nov 30, 2018 at 10:00 AM Robin Chan <rc...@redhat.com> wrote: > I've heard zero need for a or desire for Pulp 3 to be distributed other > than PyPI. > I've got no issues with closing an issue now and should things change in > the future we can resurrect or create a new story if needed. > > On Fri, Nov 30, 2018 at 9:40 AM Brian Bouterse <bbout...@redhat.com> > wrote: > >> Please send feedback by Dec 7th. >> >> On Thu, Nov 29, 2018 at 7:49 AM Brian Bouterse <bbout...@redhat.com> >> wrote: >> >>> The plan about 12-24 months ago was to distribute Pulp3 with Pulp itself >>> on a machine hosted in the osci.io community environment. We have this >>> ticket tracking that work [0] (still at NEW). >>> >>> I commented [1] that I think our distribution plans now involve mainly >>> PyPI releases, and we probably won't self-host our release infrastructure. >>> Is that what others think? >>> >>> If we aren't self-hosting with Pulp, can we close this ticket [0], clean >>> up the infra wiki [2], and ask OSCI to deprovision their machine? >>> >>> [0]: https://pulp.plan.io/issues/2325 >>> [1]: https://pulp.plan.io/issues/2325#note-32 >>> [2]: >>> https://pulp.plan.io/projects/pulp/wiki/Infrastructure_&_Hosting#Distribute-Pulp-with-Pulp >>> >>> Thanks! >>> Brian >>> >> _______________________________________________ >> Pulp-dev mailing list >> Pulp-dev@redhat.com >> https://www.redhat.com/mailman/listinfo/pulp-dev >> > _______________________________________________ > Pulp-dev mailing list > Pulp-dev@redhat.com > https://www.redhat.com/mailman/listinfo/pulp-dev >
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev