I started working on an RC5 release but ran out of time today. I'll finish
up and release tomorrow first thing.
David
On Tue, Sep 10, 2019 at 2:00 PM Austin Macdonald
wrote:
> There was a new feature, but it was missed because it wasn't in the
> release notes:
There was a new feature, but it was missed because it wasn't in the release
notes: https://github.com/pulp/pulpcore-plugin/pull/125
The docker plugin is already using the new filter, so a new rc would be
helpful.
On Tue, Sep 3, 2019 at 12:12 PM Ina Panova wrote:
> Thank for clarification, then
Thank for clarification, then there is no need for an extra rc release.
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 Tue, Sep 3, 2019 at 5:08 PM David Davis wrote:
>
The only core change in 4681 is that it raises an exception when there is
no default_related_name defined on a Detail model. So no plugin release
should be blocked by 4681.
David
On Tue, Sep 3, 2019 at 11:00 AM Ina Panova wrote:
> Brian,
>
> how about releasing RC5 earlier, for example
Brian,
how about releasing RC5 earlier, for example Thursday Sep 5, and putting
the blocker list to RC6?
With the recent changes happened in core [0], plugins cannot release unless
there is already a released core version that contains this change.
For example, docker plugin would like to cut
tl;dr -- Let's release pulpcore and pulpcore-plugin on Tuesday Sept 10th.
Please identify any backwards incompatible changes or high-risk changes as
blockers here [2].
It's been ~ 5 weeks since pulpcore and pulpcore-plugin have released. There
are several changes ready for each [0][1] . I
