31,029
edits
Tag: 2017 source edit |
Tag: 2017 source edit |
||
| Line 48: | Line 48: | ||
However, today the number of developments proposed and which are integrated is greater than the number of fixes or stabilizations (standardization, security, etc.) proposed while it should be 1 PR out of 3 only to be at the balance (3 = 1 for feature + 2 for stabilization). | However, today the number of developments proposed and which are integrated is greater than the number of fixes or stabilizations (standardization, security, etc.) proposed while it should be 1 PR out of 3 only to be at the balance (3 = 1 for feature + 2 for stabilization). | ||
In short, there is no understaffing on the merge (in fact the workload when you know the app well is quite low) but we will always have an understaffing on the Fixers, Debuggers and Technical Debt Killers that I would call with the initials, the '''FDK'''s for the following (FDKs are those who work, mainly during a beta phase, to make the application stable and/or coherent, correct regressions, but also during the dev phases to reduce technical debt for example). | In short, there is no understaffing on the merge (in fact the workload when you know the app well is quite low) but we will always have an understaffing on the Fixers, Debuggers and Technical Debt Killers that I would call with the initials, the "'''FDK'''s" for the following (FDKs are those who work, mainly during a beta phase, to make the application stable and/or coherent, correct regressions, but also during the dev phases to reduce technical debt for example). | ||
A merger can replace himself because it is a task that requires strong technical knowledge, history and anticipatory vision of course, but little mobilization. | A merger can replace himself because it is a task that requires strong technical knowledge, history and anticipatory vision of course, but little mobilization. | ||