31,029
edits
Category:RoadMap: Difference between revisions
Jump to navigation
Jump to search
m
→Why 2 releases per year ? The limitation of FDK ?
Tag: 2017 source edit |
Tag: 2017 source edit |
||
| Line 49: | Line 49: | ||
However, today the number of enhancement proposed (and which are integrated) is greater than the number of fixes or stabilization (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 enhancement proposed (and which are integrated) is greater than the number of fixes or stabilization (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 under-staffing on the merge (in fact the workload when you know the app well is quite low) but we will always have an under-staffing on the '''Fixers''', '''Debuggers''' and '''Technical Debt | In short, there is no under-staffing on the merge (in fact the workload when you know the app well is quite low) but we will always have an under-staffing on the '''Fixers''', '''Debuggers''' and '''Killers of Technical Debt''' 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 development phases to reduce technical debt for example). | ||
The merger can be replaced because it is a task that requires strong technical knowledge, history and anticipatory vision of course, but a little mobilization compared to size of the project (2 half days per week). | The merger can be replaced because it is a task that requires strong technical knowledge, history and anticipatory vision of course, but a little mobilization compared to size of the project (2 half days per week). | ||