Difference between revisions of "Common CheckIn Rules"
From Apache OpenOffice Wiki
| (6 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| + | {{delete|Extremely outdated}} | ||
| + | {{Old|EN}} | ||
== Common Checkin Rules == | == Common Checkin Rules == | ||
| + | |||
| + | * See [[Mercurial/Cws]] for the common commit format on [[Mercurial]]. | ||
* Every commit is been done with a comment, which shortly describes the change. | * Every commit is been done with a comment, which shortly describes the change. | ||
| Line 7: | Line 11: | ||
* large code changes, or changes with uncertain impact should be integrated early in the life cycle of the Development codeline. | * large code changes, or changes with uncertain impact should be integrated early in the life cycle of the Development codeline. | ||
| − | * The | + | * The Release Status Meeting (see [[ReleaseStatus Minutes]]) or the [[Release Manager]] can reject the integration of child workspaces. |
| + | |||
| + | [[Category:Releases]] | ||
| + | [[Category:Policy]] | ||
Latest revision as of 09:58, 4 August 2022
This article is outdated. Common Checkin Rules
- See Mercurial/Cws for the common commit format on Mercurial.
- Every commit is been done with a comment, which shortly describes the change.
- Every commit has a corresponding issue, the issue will be mentioned in the commit comment with #ixxxx#, where xxxx is the Issue ID.
- large code changes, or changes with uncertain impact should be integrated early in the life cycle of the Development codeline.
- The Release Status Meeting (see ReleaseStatus Minutes) or the Release Manager can reject the integration of child workspaces.
