[Pulp-dev] is 3.0-dev branch ready to become master?

[Dennis Kliban]

We need to start planning the creation of  a "2.17-dev" branch from the
current master and merging "3.0-dev" into "master". We would then create
new "2.Y-dev" branch after each "2.Y.0" release. All 3.0 work would then
land on master.

Do our release engineering tools support this change? If not, what would it
take to support it?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20180521/4a22ae6d/attachment.htm>