30,997
edits
Language and development rules: Difference between revisions
Jump to navigation
Jump to search
m
→Rules to define if a contribution is in a maintenance or develop branch
Tag: 2017 source edit |
Tag: 2017 source edit |
||
| Line 626: | Line 626: | ||
Here again, it is the experience and the observation of a better productivity performance that has motivated the abandonment of the external Presentation frameworks in favor of the PHP framework. | Here again, it is the experience and the observation of a better productivity performance that has motivated the abandonment of the external Presentation frameworks in favor of the PHP framework. | ||
=Rules to define | =Rules to define branch target of a contribution= | ||
The rules to decide if a contribution (Pull Request) must be pushed into an old maintenance branch or into development are not strict and are often defined by the good sense (pragmastism first). We can how | The rules to decide if a contribution (Pull Request) must be pushed into an old maintenance branch or into development are not strict and are often defined by the good sense (pragmastism first). We can how | ||
be help by this [[Decision algorithm for branch choice of a PR]]. | be help by this [[Decision algorithm for branch choice of a PR]]. | ||