On Sun, Jan 23, 2022 at 6:58 PM Takashi Kajinami tkajinam@redhat.com wrote:

Hello,

I already discussed this with a few cores last year but I'm raising this topic in ML to make an official decision.

Currently Puppet OpenStack is following cycle-with-intermediary and creates a release every milestone. However our code is tightly related to the actual service implementations and having only puppet releases is not very useful.

Considering the above point, and effort required to cut off releases per milestone, I'll propose changing our release model to cycle-with-rc , and creating a single release.

Because we already created milestone releases for Yoga, I'm thinking of applying the change from next cycle(Z).

Works for me.

Please let me know if you have any concerns.

Thank you, Takashi

On 1/24/22 02:55, Takashi Kajinami wrote:

Hello,

I already discussed this with a few cores last year but I'm raising this topic in ML to make an official decision.

Currently Puppet OpenStack is following cycle-with-intermediary and creates a release every milestone. However our code is tightly related to the actual service implementations and having only puppet releases is not very useful.

Considering the above point, and effort required to cut off releases per milestone, I'll propose changing our release model to cycle-with-rc , and creating a single release.

Because we already created milestone releases for Yoga, I'm thinking of applying the change from next cycle(Z).

Please let me know if you have any concerns.

Thank you, Takashi

+1

Thank you, all, who shared your thoughts on this !

Because we haven't heard any concerns or objections, we'll move this transition forward. As I mentioned earlier, I'm expecting the change will be applied from the Z release.

Thank you, Takashi

On Mon, Jan 24, 2022 at 10:55 AM Takashi Kajinami tkajinam@redhat.com wrote:

Hello,

I already discussed this with a few cores last year but I'm raising this topic in ML to make an official decision.

Currently Puppet OpenStack is following cycle-with-intermediary and creates a release every milestone. However our code is tightly related to the actual service implementations and having only puppet releases is not very useful.

Considering the above point, and effort required to cut off releases per milestone, I'll propose changing our release model to cycle-with-rc , and creating a single release.

Because we already created milestone releases for Yoga, I'm thinking of applying the change from next cycle(Z).

Please let me know if you have any concerns.

Thank you, Takashi