From bbb22f291ec0aeb337f1d7e86200f61163dd57e8 Mon Sep 17 00:00:00 2001 From: timothymctim Date: Mon, 17 Apr 2017 19:23:19 +0200 Subject: [PATCH 1/2] Update deployment.rst Fix typos and style. --- deployment.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/deployment.rst b/deployment.rst index f5d1b74cea0..1d8db609c34 100644 --- a/deployment.rst +++ b/deployment.rst @@ -80,7 +80,7 @@ specifically tailored to the requirements of Symfony. `Capistrano`_ with `Symfony plugin`_ `Capistrano`_ is a remote server automation and deployment tool written in Ruby. `Symfony plugin`_ is a plugin to ease Symfony related tasks, inspired by `Capifony`_ - (which works only with Capistrano 2 ) + (which works only with Capistrano 2). `sf2debpkg`_ Helps you build a native Debian package for your Symfony project. @@ -181,12 +181,12 @@ setup: * Pushing assets to a CDN * ... -Application Lifecycle: Continuous Integration, QA, etc ------------------------------------------------------- +Application Lifecycle: Continuous Integration, QA, etc. +------------------------------------------------------- While this entry covers the technical details of deploying, the full lifecycle -of taking code from development up to production may have a lot more steps -(think deploying to staging, QA (Quality Assurance), running tests, etc). +of taking code from development up to production may have a lot more +steps—think deploying to staging, QA (Quality Assurance), running tests, etc. The use of staging, testing, QA, continuous integration, database migrations and the capability to roll back in case of failure are all strongly advised. There From b0f141b804edf5218b4ca422431553e3ddba4630 Mon Sep 17 00:00:00 2001 From: Javier Eguiluz Date: Tue, 18 Apr 2017 09:41:19 +0200 Subject: [PATCH 2/2] Minor reword --- deployment.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/deployment.rst b/deployment.rst index 1d8db609c34..6375056934c 100644 --- a/deployment.rst +++ b/deployment.rst @@ -185,8 +185,8 @@ Application Lifecycle: Continuous Integration, QA, etc. ------------------------------------------------------- While this entry covers the technical details of deploying, the full lifecycle -of taking code from development up to production may have a lot more -steps—think deploying to staging, QA (Quality Assurance), running tests, etc. +of taking code from development up to production may have more steps: +deploying to staging, QA (Quality Assurance), running tests, etc. The use of staging, testing, QA, continuous integration, database migrations and the capability to roll back in case of failure are all strongly advised. There