db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rick Hillegas <Richard.Hille...@Sun.COM>
Subject Re: Signal to noise on derby-dev
Date Mon, 20 Mar 2006 18:40:49 GMT
I think that, for a maintenance release, the old model is a fine way to 
generate Release Notes: there JIRAs pretty much correspond to fixed 
bugs. But for a major development effort, a big shower of granular 
subtasks will probably confuse customers. Alas, this complicates the 
10.2 release manager's job!


Daniel John Debrunner wrote:

>Rick Hillegas wrote:
>>I would be surprised if the subject lines of these granular JIRAs made
>>their way into the Release Notes. We subdivide tasks into bite-sized
>>JIRAs to help developers and reviewers digest large features. I think
>>we'll just confuse our customers if we expose this detail of our
>>development process. For the sample JIRA below, I don't think the
>>customer will appreciate either the existing subject line or the
>>proposed replacement. Instead, I would recommend that the Release Notes
>>provide some composite summary, describing which high level JDBC4
>>features we support and which we don't.
>That's what has been done for the past Derby releases, create the
>release notes using Jira's facility to do that. Of course additional
>text can be added into the release notes.

View raw message