I think including a date in the name is a bit much. Personally, I like
<patchname>_v<num>, and let the hover mechanism let you know the date.
As a committer it would be nice to have the bug description in the patch
name, but if necessary I can do that when I save the patch to my local
filesystem.
David
Daniel John Debrunner wrote:
Kathey Marsden wrote:
Mamta Satoor wrote:
What I have been doing with my patches is to keep all the revisions in JIRA
but try to name such that (hopefully) it is easier for the reviewers to see
what is the latest patch. The naming convention I use has bug number, little
info about bug and date it was created. for eg
Derby479LinkageErrorReturnNullIfNulldiff021306.txt
I really like the issue number and date in the name as you have it. It
really helps me keep patches straight.
I would add
- A patch number so Jira sorts in the right order.
I'm not sure Jira guarantees any sort order.
If you hover the pointer over the attachment the date it was attached
pops up, I find that useful for confirming the latest version.
Also, I think if you attach a file of the same name the older version is
greyed out, not sure if you can still select it or not. Though I do
recommend different names for patches, versions or dates. Dates can be
somewhat confusing unless everyone sticks to international format of
year followed by month followed by day.
Dan.
begin:vcard
fn:David W Van Couvering
n:Van Couvering;David W
org:Sun Microsystems, Inc.;Database Technology Group
email;internet:[EMAIL PROTECTED]
title:Senior Staff Software Engineer
tel;work:510-550-6819
tel;cell:510-684-7281
x-mozilla-html:TRUE
version:2.1
end:vcard
