31,029
edits
| Line 48: | Line 48: | ||
* Projet | * Projet | ||
=> Versionning (next = 5.0 ? Give a fun nickname like "The Naked Nerd") => LDR: Yes. 5.0 | => Versionning (next = 5.0 ? Give a fun nickname like "The Naked Nerd") => LDR: Yes. 5.0 | ||
=> Give some community developers admiral role for simple bugfix merge allows more reactivity and give L.DESTAILLEUR more time to focus on new features and roadmap => NO: | => Give some community developers admiral role for simple bugfix merge allows more reactivity and give L.DESTAILLEUR more time to focus on new features and roadmap | ||
As i said hundred of time | |||
=> NO: As i said hundred of time MERGING PROCESS DOES NOT NEED TIME. It is even the opposite. Letting merging on a core branch by several people increase problems and the time required to merge (merging must be validated 2 times and revert must be often do, frequently manually). I spend around 3 mn per day for merging PRs so this point is ABSOLUTELY NOT A PROBLEM. To provide me more time, what i need is bug fixes or development on dedicated taks/issues. I fixed around 2 hundred of bugs at each version and this IS CONSUMING TIME. We must not compare time spent to merge and delay to merge (time is around 3mn per day, probably less), and delay to merge is often delayed on purpose for several reason: let people and other developper or user give their point of view, to avoid too fast decision when introducing a change, to wait another PR being fixed, and ton of other reason. But this won't change. Focusing on this is a lost of time. Merging PR does not need time, I spend more time to repeat this so many time than to make merging of a full one month set of PRs ;-) | |||
* Salons | * Salons | ||