Pulp

bmbouter wrote:

Similarly the spec files must be removed from the branches each plugin will use for its 3.0 release also.

In general I think that creating a branch with whatever the next major version is for each plugin will work. The only exception I can think of right now might be python. If all the work that asmacdo's done there is backward-incompatible, then we'll want to account for that when picking the branch major version.

semyers wrote:

bmbouter wrote:

Similarly the spec files must be removed from the branches each plugin will use for its 3.0 release also.

In general I think that creating a branch with whatever the next major version is for each plugin will work. The only exception I can think of right now might be python. If all the work that asmacdo's done there is backward-incompatible, then we'll want to account for that when picking the branch major version.

In talking with ipanova, I'm rejecting my own idea. It'll be way easier if we just do all development for 3.0 on all projects (platform, plugins, etc.) on a branch named '3.0-dev'. bmbouter, what do you think?

@smyers yes please use 3.0-dev for all plugins! That sounds like a great idea. We can make the branch names accurate to the plugin versions later when we promote the 3.0-dev branches.

3.0-dev branch created for docker, rpm, puppet, ostree, python plugins.

https://github.com/pulp/pulp_docker/pull/175
https://github.com/pulp/pulp_rpm/pull/958
https://github.com/pulp/pulp_puppet/pull/241
https://github.com/pulp/pulp_ostree/pull/74
https://github.com/pulp/pulp_python/pull/90