Timeline for Is it wrong to put all projects in one VSTS project and then create nested epics
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 12, 2019 at 14:46 | comment | added | DPH | I'm a PO type myself, so not best person to talk about Pipelines. They're used in the continuous integration/delivery area to test integration builds and automate aspects of deployment. RE: releases, you can think of them as being a collection of features being delivered after N sprints. So you could tag your features (or stories below them) with a "R1: Dashboard" tag and then easily see what makes up that release. | |
| Feb 12, 2019 at 14:05 | comment | added | Mathematics | +1 and ta for your answer, there are few things which I am not able to understand correctly e.g. how project is related to releases and pipelines, we can create different releases and pipelines for different templates for different types of solutions in a project | |
| Feb 12, 2019 at 13:16 | history | answered | DPH | CC BY-SA 4.0 |