From 3303d40287d5c952cdfc4ef29dd01eb116ad2035 Mon Sep 17 00:00:00 2001 From: Kathryn Elliott Date: Mon, 2 Jul 2018 01:23:14 +0000 Subject: [PATCH 1/2] Merged PR 359770: Add Upgrade Hosed-to-Inheritance topics to TOC and Index small github fix --- docs/work/customize/index.md | 3 +++ docs/work/customize/toc.yml | 6 ++++++ .../work-items/guidance/cmmi/guidance-background-to-cmmi.md | 2 +- 3 files changed, 10 insertions(+), 1 deletion(-) diff --git a/docs/work/customize/index.md b/docs/work/customize/index.md index 35c1be66a72..5546c4e0de1 100644 --- a/docs/work/customize/index.md +++ b/docs/work/customize/index.md @@ -63,6 +63,9 @@ Use the guidance provided in the following topics based on the process model or - [Create and manage a process](../../organizations/settings/work/manage-process.md?toc=/vsts/work/customize/toc.json&bc=/vsts/work/customize/breadcrumb/toc.json) - **Hosted XML process model** + - [Supported upgrade operations](../../organizations/settings/work/upgrade-support-hosted-to-inherited.md?toc=/vsts/work/customize/toc.json&bc=/vsts/work/customize/breadcrumb/toc.json) + - [Upgrade a Hosted XML process to Inheritance](../../organizations/settings/work/upgrade-hosted-to-inherited.md?toc=/vsts/work/customize/toc.json&bc=/vsts/work/customize/breadcrumb/toc.json) + - [Change a project from Hosted XML to Inheritance](../../organizations/settings/work/change-process-from-hosted-to-inherited.md?toc=/vsts/work/customize/toc.json&bc=/vsts/work/customize/breadcrumb/toc.json) - [Customize a Hosted XML process](import-process/customize-process.md) - [Import a process](import-process/import-process.md) diff --git a/docs/work/customize/toc.yml b/docs/work/customize/toc.yml index 21f9fe6d7a9..20facd2842f 100644 --- a/docs/work/customize/toc.yml +++ b/docs/work/customize/toc.yml @@ -71,6 +71,12 @@ - name: Hosted XML process model href: hosted-xml-process-model.md items: + - name: Supported upgrade operations + href: ../../organizations/settings/work/upgrade-support-hosted-to-inherited.md?toc=/vsts/work/customize/toc.json&bc=/vsts/work/customize/breadcrumb/toc.json + - name: Upgrade a Hosted XML process to Inheritance + href: ../../organizations/settings/work/upgrade-hosted-to-inherited.md?toc=/vsts/work/customize/toc.json&bc=/vsts/work/customize/breadcrumb/toc.json + - name: Change a project from Hosted XML to Inheritance + href: ../../organizations/settings/work/change-process-from-hosted-to-inherited.md?toc=/vsts/work/customize/toc.json&bc=/vsts/work/customize/breadcrumb/toc.json - name: Customize a Hosted XML process href: import-process/customize-process.md?toc=/vsts/work/customize/toc.json&bc=/vsts/work/customize/breadcrumb/toc.json - name: Import a process diff --git a/docs/work/work-items/guidance/cmmi/guidance-background-to-cmmi.md b/docs/work/work-items/guidance/cmmi/guidance-background-to-cmmi.md index b8d9b6eba03..0927121a5a2 100644 --- a/docs/work/work-items/guidance/cmmi/guidance-background-to-cmmi.md +++ b/docs/work/work-items/guidance/cmmi/guidance-background-to-cmmi.md @@ -16,7 +16,7 @@ ms.date: 01/20/2017 [!INCLUDE [temp](../../../_shared/dev15-version-header.md)] -The definitive guide to the Capability Maturity Model Integration (CMMI) for Development is published by the Software Engineering Institute as "CMMI: Guidelines for Process Integration and Product Improvement." This book specifically describes the CMMI for Development (CMMI-DEV) version 1.3, which is one of the models within the current CMMI product suite at the time of this writing. This model is extremely stable and should continue to be current well beyond 2010. You may also find "CMMI Distilled: A Practical Introduction to Integrated Process Improvement" to be a useful and accessible book about the topic. For more information about both of these books, see [Additional resources](#resources) later in this topic. +The definitive guide to the Capability Maturity Model Integration (CMMI) for Development is published by the Software Engineering Institute as "CMMI: Guidelines for Process Integration and Product Improvement." This book specifically describes the CMMI for Development (CMMI-DEV) version 1.3, which is one of the models within the current CMMI product suite at the time of this writing. This model is extremely stable and should continue to be current well beyond 2010. You may also find "CMMI Distilled: A Practical Introduction to Integrated Process Improvement" to be a useful and accessible book about the topic. The CMMI started life in 1987 as the Capability Maturity Model (CMM), a project at the Software Engineering Institute, which is a research center at Carnegie-Mellon University. This center was established and funded by the United States Department of Defense. The CMM for Software was first published in 1991 and is based on a checklist of critical success factors in software development projects during the late 70s and early 80s. The model is also informed by research at International Business Machines (IBM) Corporation and 20th-century quality assurance leaders Philip Crosby and W. Edwards Deming. Both the name, Capability Maturity Model, and the five levels in the Staged Representation (as discussed later in this topic) were inspired by Crosby's Manufacturing Maturity Model. Applied mainly to defense programs, CMM has achieved considerable adoption and undergone several revisions and iterations. Its success led to the development of CMMs for a variety of subjects beyond software. The proliferation of new models was confusing, so the government funded a two-year project that involved more than 200 industry and academic experts to create a single, extensible framework that integrated systems engineering, software engineering, and product development. The result was CMMI. From 43c8769e1108b00d0d9542af1dd6839c971c7f69 Mon Sep 17 00:00:00 2001 From: Andy Lewis Date: Mon, 2 Jul 2018 14:44:25 +0000 Subject: [PATCH 2/2] Merged PR 360297: Small clarification to designer get started based on feedback from a reader UX clarification based on feedback from a reader [Conversation]:="feedback on hello world build tutorial we were discussing" --- docs/pipelines/get-started-designer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pipelines/get-started-designer.md b/docs/pipelines/get-started-designer.md index 23fa4725e30..c6a6a4e1852 100644 --- a/docs/pipelines/get-started-designer.md +++ b/docs/pipelines/get-started-designer.md @@ -329,7 +329,7 @@ Write-Host Trigger: $trigger 1. **Commit** (save) the script. -1. Go to the **Build and Release** hub, and notice that a build is automatically triggered by the change that you committed. +1. Go to the **Build and Release** hub and select **Queued**. Notice under the **Queued or running** section that a build is automatically triggered by the change that you committed. 1. Select the new build that was created and view its log.