You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@river.apache.org by Sim IJskes - QCG <si...@qcg.nl> on 2011/01/13 10:19:53 UTC
documenting creating release notes
On 13-01-11 01:22, Peter Firmstone wrote:
> Can you raise a JIRA, so I've got something for the release notes.
Can you document on the wiki how you assemble those release notes?
Gr. Sim
--
QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
Re: documenting creating release notes
Posted by Sim IJskes - QCG <si...@qcg.nl>.
On 13-01-11 10:22, Peter Firmstone wrote:
> Sim IJskes - QCG wrote:
>> On 13-01-11 01:22, Peter Firmstone wrote:
>>> Can you raise a JIRA, so I've got something for the release notes.
>>
>> Can you document on the wiki how you assemble those release notes?
>>
>> Gr. Sim
>>
> I will given time, but here's are some tips for now:
>
> Release note generation:
> https://issues.apache.org/jira/secure/ConfigureReleaseNote.jspa?projectId=12310600
>
>
> We need to make sure that for external api changes, or bug fixes or
> things that affect functionality have Jira issues created. Then quote
> the issue in your commit comment:
>
> eg:
> https://issues.apache.org/jira/browse/RIVER-300?page=com.atlassian.jira.plugin.ext.subversion%3Asubversion-commits-tabpanel
>
>
> This captures everything for the release notes.
Could you create a wiki page for this?
Gr. Sim
--
QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
Re: documenting creating release notes
Posted by Peter Firmstone <ji...@zeus.net.au>.
Sim IJskes - QCG wrote:
> On 13-01-11 01:22, Peter Firmstone wrote:
>> Can you raise a JIRA, so I've got something for the release notes.
>
> Can you document on the wiki how you assemble those release notes?
>
> Gr. Sim
>
I will given time, but here's are some tips for now:
Release note generation:
https://issues.apache.org/jira/secure/ConfigureReleaseNote.jspa?projectId=12310600
We need to make sure that for external api changes, or bug fixes or
things that affect functionality have Jira issues created. Then quote
the issue in your commit comment:
eg:
https://issues.apache.org/jira/browse/RIVER-300?page=com.atlassian.jira.plugin.ext.subversion%3Asubversion-commits-tabpanel
This captures everything for the release notes.
Peter.