@wayne.wang I watched your presentation today and have some questions... when you talked about the express and freight trains were there two different pipelines to allow for the two speeds? How did the team handle working on short quick things in parallel to the longer slower work? How frequently were changes merged between the tracks? Thanks in advance for your responses.

@kbathgat, we have small release pipelines as the building block, and we assemble these small pipelines into express and freight trains based on what's been approved for release for the period. So the answer to your first question is, they are the same pipelines but consolidated into "assemblies" for the easy of release. As for working parallel, I found it's better when we have different sub-teams handle the different release trains, for avoiding too much task switching. How quickly we merge the quick changes to the long-run stuff is a function of test automation capacity. In general, we were able to do that every 2-3 weeks, but at least once before we do the big release (freight train).

@kbathgat, we have small release pipelines as the building block, and we assemble these small pipelines into express and freight trains based on what's been approved for release for the period. So the answer to your first question is, they are the same pipelines but consolidated into "assemblies" for the easy of release. As for working parallel, I found it's better when we have different sub-teams handle the different release trains, for avoiding too much task switching. How quickly we merge the quick changes to the long-run stuff is a function of test automation capacity. In general, we were able to do that every 2-3 weeks, but at least once before we do the big release (freight train).