Repository navigation
Decision Log
This page records key technical and organizational decisions made during the project.
We decided to use a GitFlow-like branching strategy consisting of main, develop, and feature/* branches.
This approach ensures controlled integration, prevents direct pushes to critical branches, and supports code review.
All changes are introduced via pull requests.
Direct pushes to main and develop branches are prohibited.
At least one approving review is required before merging to ensure code quality and team collaboration.
GitHub Projects was selected to track tasks, assign responsibilities, and visualize weekly progress using a Kanban-style board.
Project documentation is maintained using Markdown files (README.md, INSTALL.md, etc.)
and GitHub Wiki pages for weekly reports, meeting notes, and decision tracking.
Weekly meetings are documented in the GitHub Wiki to ensure transparency and maintain a clear record of discussions and decisions.
- The project will transition from setup to implementation starting Week 3.
- The C++ application will be built using CMake and linked with PostgreSQL via libpqxx.
- Unit testing and CI automation are mandatory starting from Week 3.
- Docker-based execution remains the primary runtime environment.
- Week 4 is dedicated to final verification (CI + Docker) and documentation completion.
- Final merge to main will be performed at the end of Week 4 after checks pass.
- A release tag will be created after the final merge to main.