Hi David,
you are creating a completely new process now.

Stable should be stable so fixes should be created on master and if they are 
suitable for colorado, can be cherry-picked to stable/colorado.
NOT THE OTHER WAY!
Creation of the stable branch is to freeze the code on stable.
You introduce a new window now that you open at milestone 9.
But you don’t specify when this window closes. The way you describe it, code 
freeze is achieved when the window is closed.
If a project wouldn’t have the stable branch created, that project would not 
have reached the code freeze milestone 9.
So please clarify what you intend to do to projects that miss the code freeze 
date.
And we need a new milestone when the window closes.
Effectively by saying the window opens on August 15, you shift the code freeze.

As Chris has said many times now, please let’s not change the process on the 
fly.
I don’t know how we want to do a release if we change the process that way 7 
weeks before we want to release.
We need the code freeze, so the frozen code can be tested and BUGs can be fixed.
If support for scenario is not implemented at code freeze, the related 
implementation should not be on stable/colorado, and not be in the release.

Cheers,
Uli






From: David McBride [mailto:[email protected]]
Sent: Friday, 05 August, 2016 01:31
To: Ulrich Kleber
Cc: Christopher Price; [email protected]
Subject: Re: Colorado release pipeline

Uli,

I looked at the page again and added some detail around the process for stable 
branch creation.  Also, I noticed that you said that cherry-picking should be 
done from master to branch, but I think it's the other way around, isn't it?  
Bug fixes should be applied to the branch, then cherry-picked to master, right?

David

On Mon, Aug 1, 2016 at 10:29 AM, David McBride 
<[email protected]<mailto:[email protected]>> wrote:
Uli,

Thanks for updating the page.  Looks good.

David

On Mon, Aug 1, 2016 at 1:43 AM, Ulrich Kleber 
<[email protected]<mailto:[email protected]>> wrote:
Hi,
I updated the release pipeline description in the wiki and created a link from 
colorado release page.
Please have a look.
Chris, please reserve some time in the TSC meeting tomorrow.

Cheers,
Uli



--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018<tel:%2B1.805.276.8018>
Email/Google Talk: 
[email protected]<mailto:[email protected]>
Skype: davidjmcbride1
IRC: dmcbride



--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018<tel:%2B1.805.276.8018>
Email/Google Talk: 
[email protected]<mailto:[email protected]>
Skype: davidjmcbride1
IRC: dmcbride
_______________________________________________
opnfv-tech-discuss mailing list
[email protected]
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Reply via email to