You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by Kevin Minder <ke...@hortonworks.com> on 2013/10/01 15:21:24 UTC
Jira Type field usage effect on Release Notes
Hi Everyone,
I'd like to have your help in making sure the Jira Type field is best
used to produce meaningful automated Release Notes
The Type field is the one that can be set to one of: New Feature,
Improvement, Bug, Test, Wish, Task
When the report is generated they Jira's for that release are grouped by
these Types. See the 0.3.0 report.
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314427&version=12324294
In particular it would be very helpful if the New Feature and
Improvement Types where carefully used. A user looking at these two
sections in the release not should clearly be able to see what is really
new for a release. So there should generally be some umbrella jira
marked as New Feature or Improvement with any work breakdown as Tasks.
Thanks!
Kevin.
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: Jira Type field usage effect on Release Notes
Posted by Kevin Minder <ke...@hortonworks.com>.
No. I did some manual reorganization in the CHANGES file this time around.
On 10/1/13 10:56 AM, larry mccay wrote:
> Do we need to go back through and change the types of closed issues at this
> point?
>
>
> On Tue, Oct 1, 2013 at 9:21 AM, Kevin Minder
> <ke...@hortonworks.com>wrote:
>
>> Hi Everyone,
>>
>> I'd like to have your help in making sure the Jira Type field is best used
>> to produce meaningful automated Release Notes
>> The Type field is the one that can be set to one of: New Feature,
>> Improvement, Bug, Test, Wish, Task
>>
>> When the report is generated they Jira's for that release are grouped by
>> these Types. See the 0.3.0 report.
>> https://issues.apache.org/**jira/secure/ReleaseNote.jspa?**
>> projectId=12314427&version=**12324294<https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314427&version=12324294>
>>
>> In particular it would be very helpful if the New Feature and Improvement
>> Types where carefully used. A user looking at these two sections in the
>> release not should clearly be able to see what is really new for a release.
>> So there should generally be some umbrella jira marked as New Feature or
>> Improvement with any work breakdown as Tasks.
>>
>> Thanks!
>> Kevin.
>>
>> --
>> CONFIDENTIALITY NOTICE
>> NOTICE: This message is intended for the use of the individual or entity
>> to which it is addressed and may contain information that is confidential,
>> privileged and exempt from disclosure under applicable law. If the reader
>> of this message is not the intended recipient, you are hereby notified that
>> any printing, copying, dissemination, distribution, disclosure or
>> forwarding of this communication is strictly prohibited. If you have
>> received this communication in error, please contact the sender immediately
>> and delete it from your system. Thank You.
>>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
Re: Jira Type field usage effect on Release Notes
Posted by larry mccay <la...@gmail.com>.
Do we need to go back through and change the types of closed issues at this
point?
On Tue, Oct 1, 2013 at 9:21 AM, Kevin Minder
<ke...@hortonworks.com>wrote:
> Hi Everyone,
>
> I'd like to have your help in making sure the Jira Type field is best used
> to produce meaningful automated Release Notes
> The Type field is the one that can be set to one of: New Feature,
> Improvement, Bug, Test, Wish, Task
>
> When the report is generated they Jira's for that release are grouped by
> these Types. See the 0.3.0 report.
> https://issues.apache.org/**jira/secure/ReleaseNote.jspa?**
> projectId=12314427&version=**12324294<https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314427&version=12324294>
>
> In particular it would be very helpful if the New Feature and Improvement
> Types where carefully used. A user looking at these two sections in the
> release not should clearly be able to see what is really new for a release.
> So there should generally be some umbrella jira marked as New Feature or
> Improvement with any work breakdown as Tasks.
>
> Thanks!
> Kevin.
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity
> to which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>