Back to Flutter Inner Source homepage
inner source

Development Lifecycle

The process by which you make and release a change to your application is your Software Development Lifecycle or SDLC. Within Flutter-Global several SDLC patterns are directly supported by tools such as the git flutter CLI. Using these standard SDLC patterns is recommended unless you have unusual requirements.

Typically a change will follow these steps to production:

  1. Source: A code edit is applied to a Flutter-Global repository with access controls and a branching strategy.
  2. Validate: Check proposed code changes by running a series of tests that must pass.
  3. Package: Resolve any external dependencies to build a new version of the desired deployment package(s) e.g. binaries, docker, rpm, jar.
  4. Component Tests: Run available tests against the candidate deployment package with other dependent mocked packages.
  5. Publish: Publish the tested deployment package to a registry so it is available to all who deploy it.
  6. Deploy: Configure the package and deploy it to a specific topology (e.g. AWS, on-prem VM, k8s).
  7. Integration Tests: Run available integration and non-functional checks.
  8. Release: Promote the deployment through the required environments to rollout to production traffic.
  9. Observe: Observe the release with heightened operational awareness to confirm success, with rollback invoked on suspicion of failure.

The standard SDLCs patterns cover steps (1)-(5), step (6) onwards is regarded as team/division specific and dependent on local requirements.


Your source code is stored in a repository within the Flutter-Global organisation. This will have:

  1. a branching strategy (where code is contributed to and merged into)
  2. an access control strategy (who can access the repository with what permissions)
  3. branch protections to ensure the combination of (1) and (2) is secure.

Three source management patterns are available: multiple teams, service or audited.

Read more about source control ➜


A proposed code change is validated by a series of checks. Common examples are linters, compile checks, unit tests, and security scans.

Read more about validation ➜

Package & Publish

A new version is packaged as a deployable artefact (e.g. a container image). This package must then be published to a location from which it can be deployed to relevant environments.

Read more about packaging and publishing ➜