Carsten,
I agree with the last three points, but not with the first two. I agree that
it makes sense to track "important" changes in JIRA, but for example the
minor change I did lately in the logger framework. In this case I don't
want to open an issues, remove the single word from the source code,
commit, go through the issue tracking process etc.
What about using a plain old change log?
Sure, this is a little more overhead. We can also do the changelog
method, and I suggest a xdocs/.changelog.xml, since we are already using
Maven, and we can use the announcement plugin.
The only thing I'd say is, can we agree to do at least one or the other
for every change: either document it in JIRA, or add in the changelog
file? That way, we can take the JIRA headlines and add to the changelog
file before a release.
As per your "important" change note, the only thing is that is a very
subjective guideline (not for your specific example, which is simple,
but most cases). It'd be simpler to follow "a rule", whatever it is,
all the time. But changelog/JIRA together work as well, as long as we
all agree to do it.
Shash
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
