Difference between revisions of "Common CheckIn Rules"
From Apache OpenOffice Wiki
B michaelsen (talk | contribs) |
|||
| Line 1: | Line 1: | ||
| − | {{ | + | {{Old|EN}} |
== Common Checkin Rules == | == Common Checkin Rules == | ||
Revision as of 12:38, 9 July 2018
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.
