Imported From: http://groups.google.com/group/in-portal-dev/browse_thread/thread/eaba8ed71dcdf45d#
One of fundamental concepts of development is patch usage. Patch is
...
one file, that can contain new/changed files and after it's applied to
...
checked out version of code, then it could be either tested or
...
committed. I'm not sure how to name patch files, because multiple
...
patches could be attached to one issue (e.g. by different developers)
...
and here comes the patch file naming problem.
I think, that patch name should contain at least: *
- issue number in tracker
...
- all/part of issue title (at least, what of it is allowed to be used
...
- in filenames)
...
- date in common format, when patch was created (doesn't necessarily
...
- is the date, when it was uploaded to tracker), t.e. 2009-10-15
...
- patch author
...
- patch version
Patch version should be used to distinguish patches, that one
developer one developer have uploaded in one issue in one day. Patch versions is
developer is developer dependent, e.g. developer "one" can have 1 version, and
developer and developer "two" also could have 1 version. Because all uploaded patch
files patch files are directly related to issue, then there is no need to further
differentiate further differentiate them in their name.
I think, that patch naming is also useful for cases, when patch is
downloaded from issue, and developer still will be able to get to
original issue.