Common CheckIn Rules

This page is a candidate for speedy deletion .

If you disagree with its speedy deletion, please explain why on its talk page and add a note to this page. If this page obviously does not meet the criteria for speedy deletion, or you intend to fix it, please remove this notice, but do not remove this notice from articles that you have created yourself.

Justification: Extremely outdated (justifications are not mandatory, but helps the administrator to evaluate).

Administrators - Remember to check if anything links here and the page history before deleting.

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.

Common CheckIn Rules

Common Checkin Rules

Views

Personal tools

Navigation

Search

Tools