[Pulp-dev] Consolidating Plugin Template Redmine Issue Tracker to Core's

Brian Bouterse bbouters at redhat.com
Tue Apr 30 13:33:59 UTC 2019

I've heard no negative feedback on this idea so I'm planning on completing
this on Thursday May 2nd.

Please reply if you have any concerns or questions.

On Fri, Apr 26, 2019 at 4:59 PM Brian Bouterse <bbouters at redhat.com> wrote:

> Currently the plugin template has its own issue tracker [0]. This is
> separate from core's issue tracker [2] which is responsible for a lot of
> things including installer, the bindings, and the dev environments.
> I propose we move all of the issues in the plugin_template tracker [0] to
> the core issue tracker [1]. Also I propose we create a tag called 'Plugin
> Template' and tag all of those issues [0] with it. Then we would delete the
> Plugin Template project.
> For both Redmine simplicity and that the plugin template (I think) belongs
> with core. Overall having more Redmine projects is more confusing and
> results in more maintenance. Also having all our issues in one Redmine
> project will let us show everything (including the plugin template) to
> stakeholder in one place [2] more easily.
> Any objections to this plan?
> [0]: https://pulp.plan.io/projects/plugin_template/issues
> [1]: https://pulp.plan.io/projects/pulp/issues
> [2]: https://pulp.plan.io/versions/57
> Cheers,
> Brian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20190430/e104a2ef/attachment.htm>

More information about the Pulp-dev mailing list