There is also a 'Packaging' Redmine project for packaging things have you seen that? https://pulp.plan.io/projects/packaging
Also w.r.t dependency issues, I imagine those would come in the form of a bug against Pulp in terms of how it affects the user. For example here is a bug in yarl files as a Pulp bug: https://pulp.plan.io/issues/4725 I wanted to share the process I imagined for those kinds of issues. I'll hold off on making an adjustment to 'External' until there is more discussion. On Fri, May 3, 2019 at 11:35 AM Mike DePaulo <mikedep...@redhat.com> wrote: > On Fri, May 3, 2019 at 11:22 AM Brian Bouterse <bbout...@redhat.com> > wrote: > > > > We have a project on Redmine called 'External' [0] which was introduced > years ago but has fallen out of use (that I know of). It has 0 open issues > against it and only 39 issues ever. These are Pulp 2 packaging issues > mostly and all items have the Pulp 2 label. > > > > To simplify our Redmine, I propose we delete this 'External' project and > move its 39 issues [1] to the Pulp Redmine project [2]. > > > > Please let me know what you think. If I don't hear any concerns or > adjustments by May 9th I'll do it then. > > > > [0]: https://pulp.plan.io/projects/external > > [1]: https://pulp.plan.io/projects/external/issues > > [2]: https://pulp.plan.io/projects/pulp > > Now that I know about it, I am very much in favor of keeping it. I > intend to start using it. > > As I have done Pulp RPM packaging in Fedora, it has been necessary to > deal with issues in Fedora. I feel they are best tracked here. > > Also, on the X2Go project, we've needed ways to track 3rd > party/dependency issues as well. > > -Mike >
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev
