Re: [Pulp-dev] Spam on plan.io

2018-10-31 Thread Austin Macdonald
On Wed, Oct 31, 2018, 2:23 PM Daniel Alley Maybe the first comment / issue posted by an account would need to be > approved, but once approved they could post subsequent comments / issues > without delay? > > @dalley, sounds right to me. I think this could be implemented using bmbouters b) option,

Re: [Pulp-dev] Spam on plan.io

2018-10-31 Thread Daniel Alley
Maybe the first comment / issue posted by an account would need to be approved, but once approved they could post subsequent comments / issues without delay? On Wed, Oct 31, 2018 at 1:28 PM, Brian Bouterse wrote: > Below is what plan.io got back to me with. I list some options below that. > > ==

Re: [Pulp-dev] Spam on plan.io

2018-10-31 Thread Brian Bouterse
Below is what plan.io got back to me with. I list some options below that. = start message === Due to the structure of our regular plans, where each additional user comes with a price attached, running Planio in combination with self registration is a very rare use case. Consequently, the

Re: [Pulp-dev] Splitting ansible-pulp3 responsibilities

2018-10-31 Thread Brian Bouterse
I've been using pulplift to test the installer, and it works excellently. The pulp3-sandbox-* boxes work great, but the pulp3-source-*installs are broken. I filed an issue here: https://pulp.plan.io/issues/4111 It would be great if all the vagrant stuff moved there since pulplift is built on Vagr

[Pulp-dev] Functional tests in redmine

2018-10-31 Thread David Davis
We’ve made a couple changes in redmine to better accommodate for pulp-smash tests. We added a new tracker type called “Test” and removed the Functional Test tag. Functional (or pulp-smash) tests should be filed using the Test tracker and the relationship between the test and the story or issue it t