It was indeed. :-)
On Apr 12, 2013 11:23 AM, "James Abley" <notifications@github.com> wrote:

> In service-manual/making-software/choosing-technology.md:
>
> > @@ -66,6 +66,18 @@ You are more likely to buy in software that fulfils a commodity need. Developmen
> >
> >  Software that requires customisation to fit your needs is best avoided. The ongoing cost of maintaining this customisation is always greater than you think it's going to be.
> >
> > +## Deployment
> > +
> > +The services that we write will need to be deployed, [early and frequently](/service-manual/making-software/release-strategies.html). Any components that we choose should be easy to deploy and upgrade as part of an [automated pipeline](/service-manual/agile/continuous-delivery.html).
> > +
> > +## Testing
> > +
> > +[Frequent, automated testing](/service-manual/making-software/testing-in-agile.html) is essential in agile development. Software that makes testing difficult should be avoided.
> > +
> > +## Playing nicely version control
>
> This feels awkward? Was it intended to be "Playing nicely with version
> control"?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/alphagov/government-service-design-manual/pull/80/files#r3769852>
> .
>