Great with the issue groomed, and much +1 feedback I think we should put it
in place soon so we can start having an accurate changelog for rc3. I am
planning to pick this up and so I've taken the issue as assigned. I'll post
PRs on this thread so everyone can see once they area available
+1
On Tue, May 28, 2019 at 2:23 PM Dennis Kliban wrote:
> +1
>
> I updated the task[0] slightly and marked it as groomed.
>
>
> [0] https://pulp.plan.io/issues/4875
>
> On Tue, May 28, 2019 at 12:14 PM Austin Macdonald
> wrote:
>
>> The proposed changes look awesome! I'm +1 for moving forward
+1
I updated the task[0] slightly and marked it as groomed.
[0] https://pulp.plan.io/issues/4875
On Tue, May 28, 2019 at 12:14 PM Austin Macdonald wrote:
> The proposed changes look awesome! I'm +1 for moving forward with it for
> pulpcore and pulpcore-plugin.
>
> If there is consensus
Today we are asking for community feedback in our second Pulp Community
Survey. The feedback we received in our first community survey provided
valuable insights into how our users use Pulp. For our second Community
Survey, we hope to also get feedback into how we can improve the upcoming
Pulp 3
The proposed changes look awesome! I'm +1 for moving forward with it for
pulpcore and pulpcore-plugin.
If there is consensus (looks like we are close), lets go ahead. If anyone
has concerns, we also have the option to implement this change for one
plugin before we go all in.
On Mon, May 27, 2019
