Re: Classification of changes in change log

Yves Forkl wrote:

> So it's no wonder Google would always redirect me to the TortoiseSVN
> project. ;-) Great invention of yours.
>
> I would like to stick to your scheme for my projects as I consider it
> highly useful. May I ask you to define the meaning of each of the tokens
> - determined by the usage you made of them - in one line or just a few
> words?
>
> (Aside the above, I also found "DEV" in TSVN's change log.)
>
> NEW:

new feature added

>
> ADD:

also new feature added, or new function
I'd say you should use NEW for features, and ADD for developer visible
changes like new functions (if you want those in the changelog)

>
> ENH:

enhancement of existing feature

>
> FIX:

a fix for a bug. Since there's also BUG, I'd use this for intermediate
fixes (if you plan to do the bugfixing another way some other time) or
if you just fix part of the bug.

>
> BUG:

bug which has been fixed

>
> CHG:

changes in functions, user interface (e.g. menu positions changed,
right-click instead of left-click, ...)

>
> MOD:

same as CHG

> DEV:

changes only visible to developers. e.g. an API change

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org