# Release Engineering

- [Introduction](/release-engineering/introduction.md): RE (Release Engineering) is the difference between building software in small teams/startups and manufacturing software in an industrial way that is repeatable, gives predictable results, and scales w
- [Git commit messages](/release-engineering/git-commit-messages.md): Writing clear and concise git commit messages is important to the overall health of a project and the team that is working on the project.
- [Code reviews & pull requests](/release-engineering/code-reviews-and-pull-requests.md): Regular, team-wide code reviews are important for the health of the software being built.
- [Trunk-based development](/release-engineering/trunk-based-development.md): From Feature-based Delivery to Timeline-based Delivery. See trunkbaseddevelopment.com for the official documentation.
- [Our methodology](/release-engineering/trunk-based-development/our-methodology.md): Following "pure" TBD is difficult without a lot of tooling, so here's the lightweight approach that we follow that relies on team discipline.
- [Service Dependencies](/release-engineering/service-dependencies.md): List of services Obvious has used in past projects
- [Tooling & infrastructure](/release-engineering/tooling-infrastructure.md)
- [Git commands & workflows](/release-engineering/git-commands-workflows.md): List of Git commands and workflows we generally use