Scope out "What should be the Build.next?"

[pradeepto]

• How should the next build look post GA/Summit?
• What should we throw away?
• What should we keep?
• What should be the experience?
• How will it scale?
• Start whiteboarding these ideas and create PoCs where possible.

[sspeiche]

Can you outline the use cases the "Build.next" needs to support? It is hard to understand what it should be without that. For example, I don't think you mean: the process by which source code is transformed to a built artifact and then packaged into a container image and stored in a registry. I think you are talking about pipelines, the ability to orchestrate either release builds, CI or CD scenarios though a workflow (pipeline) engine like Jenkins.

I would like to be included in various discussion and whiteboarding as well.

[qodfathr]

Let's not start with an Epic but rather focus on authoring real-world Scenarios with true value propositions. In fact, we already have some and we just need to augment them (both Scenarios and Fundamentals). That will lead to new Experiences, and only then can we properly come up with the new set of Features.

[chmouel]

@qodfathr your statement sounds complicated, would PM have time to provide us some of those scenarios ?

[jaseemabid]

Duplicate of #2488