[Pulp-dev] Branching Pulp 2 for plugins

[Brian Bouterse]

+1 to these changes.

Also look at the "branch protection" to port over any branch protection
configuration when the branch names change. I think mostly it's just
enabled "protect this branch" from force-push.

On Mon, Jul 2, 2018 at 10:47 AM, David Davis <daviddavis at redhat.com> wrote:

> In order to conform to the pulp/pulp repository, I propose we update our
> branches for our plugins. This would include:
>
> 1. Moving master to 2-master
> 2. Moving 3.0-dev to master (and removing 3.0-dev)
> 3. Letting @pcreech know that the branches have changed
>
> I was thinking we could do aim to do so by July 9th. Here are the plugins
> we need to update and some volunteers I have picked randomly from a hat to
> handle updating the branches:
>
> - puppet - @bizhang
> - rpm - @daviddavis
> - python - @bizhang
> - docker - @dkliban
> - ostree - @jortel
>
> I’m not sure what to do about our debian plugin though since it doesn’t
> have a 3.0-dev branch.
>
> Any feedback is welcome. Thanks.
>
> David
>
> _______________________________________________
> Pulp-dev mailing list
> Pulp-dev at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20180702/2fa2d639/attachment.htm>