After looking into this some more I believe @Simon's observation that Pulp
is operating under GPLv2+ is correct. I don't believe there is ambiguity.
There was confusion though. Specifically we include the LICENSE file in
Pulp's repo (which is GPLv2), but it's the COPYRIGHT file that actually
names
All of the various repos on the Pulp org received updates and everything
seems normal. See the details here:
https://pulp.plan.io/issues/#note-13
If you have a Pulp3 plugin that wasn't updated with ^, it likely needs some
small Travis updates. Make a patch similar to this one for pulp_file:
ht
Pulp2
- recursive copy docs https://pulp.plan.io/issues/4371 , in progress
- should be done today
- new libsolv package, QE are blocked
- if no news from the build team by the end of the week, bring up on
Monday meeting
Pulp3
- https://pulp.plan.io/issues/4424
- P
Now that we have a handful of plugins that have somewhat different
workflows, surprising user-facing differences in the interface for
plugin-related actions are becoming apparent.
Example: Publish
File:
Create a publisher
v3/publishers/file/1/publish/ repository=$REPO
Ansib
tl;dr please fork and work from https://github.com/pulp/pulpcore now. If
you had a PR open please manually re-open it since we had to make an
adjustment in the plan.
The new repo ( https://github.com/pulp/pulpcore ) is now the primary repo
for code changes for Pulp3. All Pulp3 PRs on the old repo
An issue has come up for plugins when declaring their dependence on
pulpcore-plugin.
Background:
The plugin API is semantically versioned at 0.1.0b20, which is separate
from pulpcore. The plan has always been that pulpcore would GA while the
plugin API is released as "0.1", indicating that even af
This cutover is starting in about 2 hours. I'll send instructions here when
the cutover has occurred.
On Tue, Feb 26, 2019 at 3:26 PM Brian Bouterse wrote:
> I tried to clarify the plan some. More feedback/input is welcome!
>
> On Tue, Feb 26, 2019 at 1:02 PM Neal Gompa wrote:
>
>> On Tue, Feb
+1 to the proposal
Regards,
Ina Panova
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 Wed, Feb 27, 2019 at 9:05 PM Daniel Alley wrote:
> +1
>
> On Wed, Feb 27, 2019 at 2:08 PM Brian Bouterse
> wro
