[Pulp-dev] Branching Pulp 2 for plugins
bizhang at redhat.com
Mon Jul 2 18:20:04 UTC 2018
pulp_python branching has been updated.
Note that a force push was done to push 3.0-dev to master, to get the
git fetch origin master
git reset --hard origin/master
pulp_puppet has 2-master created.
master will be updated with pulp3 bootstrap when this PR is merged:
Note that this was not done with a force push, so a regular git fetch/git
pull is sufficient to retrieve the latest master.
On Mon, Jul 2, 2018 at 1:57 PM, Dennis Kliban <dkliban at redhat.com> wrote:
> On Mon, Jul 2, 2018 at 10:47 AM, David Davis <daviddavis at redhat.com>
>> 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.
> There has only been some preliminary planning done with the debian
> plugin for Pulp 3. However, it's probably a good time to at least do some
> bootstrapping. I wrote up a task that accounts for this branch name
>  https://etherpad.net/p/pulp-deb-pulp3
>  https://pulp.plan.io/issues/3811
>> Any feedback is welcome. Thanks.
>> Pulp-dev mailing list
>> Pulp-dev at redhat.com
> Pulp-dev mailing list
> Pulp-dev at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pulp-dev