postmortem template
Status: {draft|final}
Owners: {who drove the incident resolution}
Description: {brief description of symptoms and root cause}
Component: {affected area}
Date/time: {YYYY-MM-DD HH:MM}
Duration: {time from initial breakage to final resolution}
User impact: {who was affected by the incident}
14:44 - something happened
14:45 - next thing happened <START OF OUTAGE>
09:12 - another thing happened <END OF OUTAGE>
{summarize the problems that the outage caused}
{without blame, describe the root cause of the outage}
{list things where things worked as expected in a positive manner}
{list things that mitigated this incident but not because of our foresight}
{list things that failed, with github issues from the action items section}
{each item here should have an owner}
{link to github issues for things that would have prevented this failure from happening in the first place, such as input validation, pinning dependencies, etc}
{link to github issues for things that would have detected this failure before it became An Incident, such as better testing, monitoring, etc}
{link to github issues for things that would have made this failure less serious, such as graceful degradation, better exception handling, etc}
{link to github issues for things that would have helped us resolve this failure faster, such as documented processes and protocols, etc}
{link to github issues or PRs/commits for the actual fixes that were necessary to resolve this incident}
{any other useful information, such as relevant chat logs}
- Home of the Wiki
- Roadmap
- API Reference (stable)
- API Reference (main)
- Glossary
- Contributor Guide
- Chat on Discord
- Design documents
- Code of Conduct
- Issue triage reports (latest)
- Our Values
- Tree hygiene
- Issue hygiene and Triage
- Style guide for Flutter repo
- Project teams
- Contributor access
- What should I work on?
- Popular issues
- Running and writing tests
- Release process
- Flutter Framework Gardener Rotation
- Rolling Dart
- Manual Engine Roll with Breaking Commits
- Updating Material Design Fonts & Icons
- Postmortems and Retrospectives
- Hotfix Documentation Best Practices
- In case of emergency
- Landing Changes With Autosubmit
- Setting up the Framework development environment
- The Framework architecture
- API Docs code block generation
- Running examples
- Using the Dart analyzer
- The flutter run variants
- Test coverage for package:flutter
- Writing a golden-file test for package:flutter
- Managing template image assets
- Setting up the Engine development environment
- Compiling the engine
- Debugging the engine
- Using Sanitizers with the Flutter Engine
- Testing the engine
- The Engine architecture
- Flutter's modes
- Crashes
- more...
- Setting up the Packages development environment
- Plugins and Packages repository structure
- Contributing to Plugins and Packages
- Understanding Packages tests
- Plugin Tests
- Releasing a Plugin or Package
- more...