Re: [Pulp-dev] Installer project

2020-05-13 Thread Brian Bouterse
At today's installer meeting, the installer team agreed to: * keep the installer items in the pulpcore Redmine and not have a separate Redmine for it * Add a Component named 'Installer'. New installer items should be filed with that component set. [done] * A new saved query has been created to show

Re: [Pulp-dev] Installer project

2020-05-11 Thread Ina Panova
Regards, Ina Panova Senior 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 Fri, May 8, 2020 at 3:55 PM Brian Bouterse wrote: > > > On Tue, May 5, 2020 at 10:48 AM David Davis wrote: > >> During triag

Re: [Pulp-dev] Installer project

2020-05-08 Thread Mike DePaulo
+1 to the plan. (We discussed this at PulpCon too, and concluded this.) On Fri, May 8, 2020 at 9:55 AM Brian Bouterse wrote: > > > On Tue, May 5, 2020 at 10:48 AM David Davis wrote: > >> During triage today, a majority of the issues that came up were for the >> installer but only a handful of

Re: [Pulp-dev] Installer project

2020-05-08 Thread Brian Bouterse
On Tue, May 5, 2020 at 10:48 AM David Davis wrote: > During triage today, a majority of the issues that came up were for the > installer but only a handful of people could really speak to these issues. > I proposed that we skip these issues during triage and let the installer > team triage them.

Re: [Pulp-dev] Installer project

2020-05-08 Thread David Davis
We recently made a change to the automation so that it would start checking projects and currently it's set up to check for the Pulp redmine project for pulpcore changes[0]. So currently the answer would be yes. However, we could change the commit validation to check for multiple projects. [0] htt

Re: [Pulp-dev] Installer project

2020-05-08 Thread Dennis Kliban
I am +1 to creating a new redmine project. I want to point out that we plan to move installer documentation into the main pulpcore docs. Our CI checks for issues associated with the appropriate projects. Do that mean we will need to create docs issues in the Pulp project when the docs need to be u

Re: [Pulp-dev] Installer project

2020-05-05 Thread Ina Panova
+1 to the plan. On Tue, 5 May 2020, 19:33 Fabricio Aguiar, wrote: > Yes, it makes sense > > Best regards, > Fabricio Aguiar > Software Engineer, Pulp Project > Red Hat Brazil - Latam > +55 11 999652368 > > > On Tue, May 5, 2020 at 12:24 PM David Davis wrote: > >> Cool.

Re: [Pulp-dev] Installer project

2020-05-05 Thread Fabricio Aguiar
Yes, it makes sense Best regards, Fabricio Aguiar Software Engineer, Pulp Project Red Hat Brazil - Latam +55 11 999652368 On Tue, May 5, 2020 at 12:24 PM David Davis wrote: > Cool. If we go down this path, would this plan make sense? > > 1. Create an installer project

Re: [Pulp-dev] Installer project

2020-05-05 Thread David Davis
Cool. If we go down this path, would this plan make sense? 1. Create an installer project in redmine 2. Move over all issues (opened and closed) to this project that are tagged "Pulp 3 installer" 3. Remove the "Pulp 3 installer" tag David On Tue, May 5, 2020 at 11:10 AM Fabricio Aguiar wrote:

Re: [Pulp-dev] Installer project

2020-05-05 Thread Fabricio Aguiar
+1 for creating a new project, Installer query: https://pulp.plan.io/projects/pulp/issues?query_id=154 Best regards, Fabricio Aguiar Software Engineer, Pulp Project Red Hat Brazil - Latam +55 11 999652368 On Tue, May 5, 2020 at 11:48 AM David Davis wrote: > During tri

[Pulp-dev] Installer project

2020-05-05 Thread David Davis
During triage today, a majority of the issues that came up were for the installer but only a handful of people could really speak to these issues. I proposed that we skip these issues during triage and let the installer team triage them. In order to do so, we'd have to create a separate project in