Development (DEV)
Development environment — guidelines and procedures for DEV
Development Stage Overview
The Development (DEV) stage is where new features, fixes, and improvements are developed and initially tested. This is the primary environment for engineers to build, experiment, and validate their work before it moves through the testing pipeline.
Stage Meaning
The development stage represents the latest development branch of the codebase. It contains work-in-progress features, experimental changes, and the most recent updates. This environment is less stable than staging or production but provides developers with immediate feedback on their changes.
Goals of Development Stage
- Rapid Development: Enable fast iteration and quick feedback cycles
- Early Testing: Identify and fix issues early in the development process
- Integration Testing: Test how new features integrate with existing systems
- Experimentation: Provide a safe space to try new approaches and technologies
- Continuous Feedback: Catch regressions and integration issues quickly
- Documentation: Ensure new features are properly documented as they're developed
Content in This Section
In this section you'll find guidelines and procedures for:
- Repository technical documentation and architecture guides
- Setup and development environment configuration
- API documentation and integration guides
- Feature documentation and technical specifications
- Development best practices and coding guidelines
- Testing procedures and debugging guides
Contributing to Development Documentation
Development documentation should be comprehensive and kept up-to-date as features evolve. When contributing:
- Feature Documentation: Document new features as they're developed
- API Changes: Update API documentation when endpoints or schemas change
- Architecture Updates: Document significant architectural changes or improvements
- Setup Instructions: Maintain clear setup and onboarding documentation
- Development Guides: Keep guides for common development tasks current
- Known Issues: Document known issues and limitations in development
Documentation Requirements
- Maintain a comprehensive setup guide for new developers
- Document all public APIs and their usage
- Include architecture diagrams and system design documentation
- Keep troubleshooting guides and common issues up-to-date
- Document development tools, scripts, and automation
- Add Quick Start guide for common workflows
- Maintain a Changelog documenting all significant updates