[Pulp-dev] pulpcore branching expected tomorrow Nov 13th

[Brian Bouterse]

I've branched pulpcore and pulp_file creating the 3.0 branches below. I've
modified the branch protection rules to have the same rules apply to all
branches for now ['master', '3.0']. We may need to adjust the branch
protection on 3.0 as I operate the cherry picking process later, but this
will work for now. My next steps are to touch up the versions on each
branch, sanity the changelog for pulpcore and pulp_file, and release each
to pypi. The releasing is expected to occur tomorrow AM, eastern time. I'll
announce on pulp-dev once they are available.

https://github.com/pulp/pulpcore/tree/3.0
https://github.com/pulp/pulp_file/tree/3.0

One piece of work from yesterday's list was deferred to either 3.1 or to be
cherry picked later pending more discussion.
https://github.com/pulp/pulpcore/pull/365  It's an additive plugin API
change which could arguably be a bugfix so this seems ok.

Thanks to everyone working so hard to make this possible. Next up plugin
branching!


On Tue, Nov 12, 2019 at 4:47 PM Brian Bouterse <bmbouter at redhat.com> wrote:

> Today was our target branch date for pulpcore. We are delaying branching
> pulpcore for one day, waiting on the following PRs to merge. Once branched
> I'll send an update tomorrow and then prepare the RC8 release.
>
> #pulpcore PRs:
> https://github.com/pulp/pulpcore/pull/365
> https://github.com/pulp/pulpcore/pull/369
> https://github.com/pulp/pulpcore/pull/377
> https://github.com/pulp/pulpcore/pull/380
>
> # pulp_file PRs:
> https://github.com/pulp/pulp_file/pull/307
> https://github.com/pulp/pulp_file/pull/311
>
> Feedback and suggestions are welcome.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20191113/b6d59d73/attachment.htm>