[Ansible-service-broker] Release branch and PRs

[jesus m. rodriguez]

My thought was that TP will go in release-0.9. Then stuff for GA will end up in master. Once we get close to finishing it we branch to release-1.0. At that point GA changes go to release-1.0 branch and next release goes into master.  The cycle continues. 


-------- Original Message --------
From: Ryan Hallisey <rhallise at redhat.com>
Sent: Thu Jun 22 06:13:51 EDT 2017
To: Erik Nelson <ernelson at redhat.com>
Cc: "jesus m. rodriguez" <jesusr at redhat.com>, ansible-service-broker at redhat.com
Subject: Re: [Ansible-service-broker] Release branch and PRs

If GA is suppose to be 1.0, then are we going to re tag 0.9 to be 1.0
and merge all the new stuff in master for that release?
Also, do we need a branch with that code so we can do backports
however we're going to do them?

Sincerely,
-Ryan

On Wed, Jun 21, 2017 at 8:55 PM, Erik Nelson <ernelson at redhat.com> wrote:
>> The branch will be named release-0.9 unless that's objectionable.
>
> +1
>
> _______________________________________________
> Ansible-service-broker mailing list
> Ansible-service-broker at redhat.com
> https://www.redhat.com/mailman/listinfo/ansible-service-broker