Difference between revisions of "Common CheckIn Rules"
From Apache OpenOffice Wiki
| Line 7: | Line 7: | ||
* 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. |
Revision as of 13:56, 27 July 2007
Common Checkin Rules
- 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.
