Sent from my mobile device, please forgive errors and brevity. On Sep 16, 2011 8:49 PM, "Suresh Marru" <[email protected]> wrote: > > > On Sep 16, 2011, at 2:55 PM, Marlon Pierce wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > As you should know, Jira can show SVN commits that are associated with a particular issue: just put the issue number in the commit message. See for example Airavata-93. I have two proposals: > > > > 1. I propose that every SVN commit be associated with specific (and closable) Jira tasks. > + 1, I think we should really do this, among others things, looking at JIRA will give a good picture of where one can volunteer. > >
Careful - a quick javadoc update, for example, should not require an issue to be created. A less clear case would be an edge case bug fix found during the implementation of a new feature, do we require a new issue? Do we really want to record the bug if it is discovered and fixed in one go? Good for statistical analysis of bug density, but a pain for the developer. I suggest a policy of "should" rather than "will". > > 2. While it is possible for Jira to handle multiple task definitions in a single commit message (like "(AIRAVATA-99)(AIRAVATA-100)(AIRAVATA-101) fixing lots of bugs...."), I propose we should under normal circumstances only associate one Jira task with each commit. > > + 0. I think this will be ideal, but may be harder to achieve. I will say + 1 for this approach if we literally take into account "under normal circumstances" clause. There will be cases where one commit might address few issues, but as much as possible we should shoot for one on one svn commit vs JIRA. There might be multiple commits to address one JIRA, but at least in the initial phases of development and integration, we might have multiple mappings. > In well disciplined open development one would work on a single issue at a time and commit early and often. Not doing this makes it very difficult to do code reviews. Ross > But nevertheless, I will say many +1's for fist proposal. Every commit should at least have one JIRA associated. > > Suresh > > > This will help us easily keep track of changes between release versions, for example. > > > > > > Marlon > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG/MacGPG2 v2.0.16 (Darwin) > > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > > > iQEcBAEBAgAGBQJOc5u+AAoJEEfVXEODPFIDcN4H/23JbU9TUESsWR8mkdUw8XMI > > ZWwpZwlUi5m+d+KistwAxZQJdQoZ2OXJFrO/iC46ULuwQlq154GGy2QMBpBt/n/h > > wCdmJVGJ5f4JLpN1XX2OBoqDEnVva0twy1j36FUIYujNerSDK3JOOhck3RllKsIM > > 1LucJpkV8Vnao5BwTSLDTPFTJZmcgSF5ZgxiGWnuNBKEPQohVNAwRuyNT5BI/rBt > > V9asnlDKbURM+YwxgxOFfhECJNk9SVhha/D6lIdmOdro79e7yIBkmD3/aAeRCRC+ > > eFm4TMwTzTNZB4BqhXfliy+XTJXiapZzPiWwuVQ2Q449xV3rZt8YJohk6BUlq9Y= > > =ZFI1 > > -----END PGP SIGNATURE----- > On Sep 16, 2011 8:49 PM, "Suresh Marru" <[email protected]> wrote: > > On Sep 16, 2011, at 2:55 PM, Marlon Pierce wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> As you should know, Jira can show SVN commits that are associated with a particular issue: just put the issue number in the commit message. See for example Airavata-93. I have two proposals: >> >> 1. I propose that every SVN commit be associated with specific (and closable) Jira tasks. > + 1, I think we should really do this, among others things, looking at JIRA will give a good picture of where one can volunteer. >> >> 2. While it is possible for Jira to handle multiple task definitions in a single commit message (like "(AIRAVATA-99)(AIRAVATA-100)(AIRAVATA-101) fixing lots of bugs...."), I propose we should under normal circumstances only associate one Jira task with each commit. > > + 0. I think this will be ideal, but may be harder to achieve. I will say + 1 for this approach if we literally take into account "under normal circumstances" clause. There will be cases where one commit might address few issues, but as much as possible we should shoot for one on one svn commit vs JIRA. There might be multiple commits to address one JIRA, but at least in the initial phases of development and integration, we might have multiple mappings. > > But nevertheless, I will say many +1's for fist proposal. Every commit should at least have one JIRA associated. > > Suresh > >> This will help us easily keep track of changes between release versions, for example. >> >> >> Marlon >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG/MacGPG2 v2.0.16 (Darwin) >> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ >> >> iQEcBAEBAgAGBQJOc5u+AAoJEEfVXEODPFIDcN4H/23JbU9TUESsWR8mkdUw8XMI >> ZWwpZwlUi5m+d+KistwAxZQJdQoZ2OXJFrO/iC46ULuwQlq154GGy2QMBpBt/n/h >> wCdmJVGJ5f4JLpN1XX2OBoqDEnVva0twy1j36FUIYujNerSDK3JOOhck3RllKsIM >> 1LucJpkV8Vnao5BwTSLDTPFTJZmcgSF5ZgxiGWnuNBKEPQohVNAwRuyNT5BI/rBt >> V9asnlDKbURM+YwxgxOFfhECJNk9SVhha/D6lIdmOdro79e7yIBkmD3/aAeRCRC+ >> eFm4TMwTzTNZB4BqhXfliy+XTJXiapZzPiWwuVQ2Q449xV3rZt8YJohk6BUlq9Y= >> =ZFI1 >> -----END PGP SIGNATURE----- >
