[Pulp-dev] Pulpcore RC5 Release Planning
ipanova at redhat.com
Tue Sep 3 14:59:28 UTC 2019
how about releasing RC5 earlier, for example Thursday Sep 5, and putting
the blocker list to RC6?
With the recent changes happened in core , plugins cannot release unless
there is already a released core version that contains this change.
For example, docker plugin would like to cut another beta but it is waiting
on  being included and released in core.
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 Mon, Sep 2, 2019 at 6:22 PM Brian Bouterse <bmbouter at redhat.com> wrote:
> 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 .
> It's been ~ 5 weeks since pulpcore and pulpcore-plugin have released.
> There are several changes ready for each  . I propose we release both
> on Sept 10th.
> # Blockers
> I made the blockers list here , and I put
> https://pulp.plan.io/issues/5008 on it. It's possible this may be the
> last RC (I'm not sure) so any significant change in pulpcore that we know
> about should be a blocker. Please identify those by putting them onto the
> # Upgrade form RC4 -> RC5
> There was no migration editing or squashing in pulpcore so I believe users
> should be able to upgrade from RC4 to RC5.
> # Plugin compatibility releases
> As this time I see no breaking changes in the changelogs  so as of
> now, it should not require plugins to produce compatibility releases.
> Concerns, questions, or any kind of feedback is welcome either on-list or
> : https://github.com/pulp/pulpcore/tree/master/CHANGES
> : https://github.com/pulp/pulpcore-plugin/tree/master/CHANGES
> : https://etherpad.net/p/pulpcore_rc5_blocker_list
> Pulp-dev mailing list
> Pulp-dev at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pulp-dev