It sounds like CHANGES.txt has been helping to resolve issues for Matt, and
taking it away will open the floodgates.
I'm not familiar enough with the Jira procedures yet, but my usual expectation
is that there will be some review between a developer marking the resolution
"resolved" and (don't know who) marking status "closed" to address just this
kind of issue. It's not "closed" until test, documentation, and bug database
issues are resolved also.
My feeling is that it is better to take pains to make Jira accurate than to try
to add checks to clean up after its inaccuracies.
- Tim.
Hi Todd,
As you know, one of the tasks of a release manager is to gather a correct
and complete statement of all changes in a release, and include them in the
Release Notes. As I've done the release management for 0.20-security, I've
had the fun of seeing all the deficiencies of both CHANGES.txt and Jira,
for this purpose.
I recommend keeping CHANGES.txt. While it is nominally redundant, it
provides a valuable check-and-balance to the deficiencies of Jira and SVN
for this purpose.
<snip>
--Matt
The information and any attached documents contained in this message
may be confidential and/or legally privileged. The message is
intended solely for the addressee(s). If you are not the intended
recipient, you are hereby notified that any use, dissemination, or
reproduction is strictly prohibited and may be unlawful. If you are
not the intended recipient, please contact the sender immediately by
return e-mail and destroy all copies of the original message.
