[Pulp-list] 2.9 branch at freeze?

[Michael Hrivnak]

There's no harm in doing it now, except the slight extra merge work that
needs to happen as you pointed out. That said, I'm not sure we have much to
gain by doing it now.

Technically we don't need to make the branch until someone is ready to
commit something that is in 2.10. Hopefully that will happen in the next
2-3 weeks.

So I don't think it makes a lot of difference. If it was me, I'd probably
wait a few days so we can reduce the backlog of unmerged PRs, but that's a
minor consideration. If you're itching to get it done, I don't see a reason
not to.

Michael

On Tue, Jun 7, 2016 at 12:24 PM, Sean Myers <sean.myers at redhat.com> wrote:

> Traditionally, we've created the x.y-dev branch after the corresponding
> pulp version is released. I was thinking it would be good to create that
> branch at the freeze point (pretty much right now) rather than waiting.
>
> Open PRs against master would have to be dealt with specially, but I think
> we can avoid mass-closing PRs with some git-merge-fu, since presumably
> anything
> already POSTed can be manually merged backward cleanly to the new dev
> branch,
> and then merged forward normally to close the PR. I'm happy to help with
> this
> if we do go ahead and create the dev branch now.
>
> So, is it branch time?
>
>
> _______________________________________________
> Pulp-list mailing list
> Pulp-list at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20160607/e975a850/attachment.htm>