Working Agreement on PR Review and Approvals:Team Availability/Jira/PR Activity
If you are on leave for more than 2 days, it’s your responsibility to catch up on project updates by checking with the team.
When moving a Jira story to In Progress, add a short comment with the current status or details. This helps others quickly understand the progress if they missed the DSM.
Raise any blockers or issues in the DSM so the team can help solve them quickly.
- Even if you’ve already updated Jira, please respond politely and constructively when teammates ask about your task progress. Open and respectful communication helps strengthen team collaboration.
All PRs must be approved by a Senior and Mid.
PRs should not stay
- Senior and Mid need to approve the PR PR Shouldn't remain
open for more than 2 days.
Releases are being managed in a round-robin manner.
BRANCHING STRATEGY:
We are following Git Flow Branching Strategy in our partner portal, that defines a strict branching strategy designed around the project release. It provides a robust framework for managing larger projects with multiple developers. Here’s a concise explanation of the Git Flow model:
...