From eb83f7385b0b6c9e9d503581678e46425b5e08e0 Mon Sep 17 00:00:00 2001 From: Maks Date: Tue, 26 Nov 2024 11:40:51 +0100 Subject: [PATCH] Update team-best-practices.md --- team-best-practices.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/team-best-practices.md b/team-best-practices.md index ee1f17529a..b3a0f08e06 100644 --- a/team-best-practices.md +++ b/team-best-practices.md @@ -120,7 +120,7 @@ Before starting coding, we should ensure all devs / contributors are aware of: - A milestone should **only** contain items we are sure to finish. - The end of a milestone triggers a new release. - - Milestone items and duration should take in account time spent in bugs fixing and support. + - Milestone items and duration should take into account time spent in bugs fixing and support. - The team should commit to the milestone duration. - If a dev finish early he/she can help others to push remaining tasks. - If a dev finish early he/she can work on specifying / integrating the next milestone.