What does our overall workflow for "doing" software look like?

[Bjwebb]

Some notes about this (may be out of date):

Our internal wiki has some specific information about deployment, but nothing about our general approach to "doing" software, through development to deployment and hosting.

There are issues for me to write up about possible agile approaches, and some software development guidlines [ie. this repository].

However, none of this actually describes our overall "pipeline" for doing software....

I drew some diagrams to help explain this ofr our June OGM. It would be good to write these up, and get them in a slightly cleaner format.

This ties into two of three? core principles of our software approach:
Testability
Reproducibility
Modulatrity ?

This also ties into our use of third party services e.g. Travis, Sentry

Reproducibility ties into dependency pinning https://github.com/OpenDataServices/developer-docs/blob/9771d75392b3cd23dec2a9dcd00804365a6df107/code-python.md#pinned-dependencies. We may want to also list other similar such practices...

See also this issue about adding more info about our deployment approach #28

Some extra questions:

• What are the risks with the services we're using? (particularly third party ones)