Checkin Procedures

Run JUnit tests before doing a checkin. You should always have a Bugzilla bug or feature request. When checking code in, use the Bugzilla bug id as the checkin comment.

Example 6.1. Example checkin comment

[ 553310 ] Set properties from parameter bindings

In addition, update the Tapestry release notes, the file web/new.html, to identify the feature request.

Be very careful when checking files in that they are checked in with the correct keyword substitution type. Files should be either binary or text; text should be checked in with keyword expansion turned on (this is the -kkv option).

When new files are added using Eclipse, it must decide whether they are binary or text. Eclipse always assumes binary unless specifically informed that a file is text. Use the Team preferences panel to set this.

Figure 6.2. Eclipse: Team Preferences

Eclipse: Team Preferences