Differences between revisions 1 and 2
Revision 1 as of 2010-12-08 22:15:05
Size: 316
Editor: JonMoore
Comment:
Revision 2 as of 2010-12-09 11:56:11
Size: 1052
Editor: JonMoore
Comment:
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:

Commits that are targeted against issues on JIRA should start the log message with the JIRA id
and title, followed by any additional comment, e.g.

{{{
HTTPCLIENT-1024: cache does not validate multiple cached variants
Cache revalidation of entries now sends etags of all cached variants
on the conditional request.
Contributed by ....
}}}

Formatting the commits this way will allow JIRA to automatically pick them up and link them from the issue. For example: [[https://issues.apache.org/jira/browse/HTTPCLIENT-1024?page=com.atlassian.jira.plugin.ext.subversion:subversion-commits-tabpanel|https://issues.apache.org/jira/browse/HTTPCLIENT-1024?page=com.atlassian.jira.plugin.ext.subversion:subversion-commits-tabpanel]].

Issue Tracking

Issue tracking takes place on the Apache JIRA instance.

Committers needing developer-level access to JIRA should create an account there, then mail the developer list to request that your account be granted the needed permissions.

Commits that are targeted against issues on JIRA should start the log message with the JIRA id and title, followed by any additional comment, e.g.

HTTPCLIENT-1024:  cache does not validate multiple cached variants
Cache revalidation of entries now sends etags of all cached variants
on the conditional request.
Contributed by ....

Formatting the commits this way will allow JIRA to automatically pick them up and link them from the issue. For example: https://issues.apache.org/jira/browse/HTTPCLIENT-1024?page=com.atlassian.jira.plugin.ext.subversion:subversion-commits-tabpanel.

IssueTracking (last edited 2010-12-09 11:56:11 by JonMoore)