Marshall Schor wrote:
Michael Baessler wrote:
Adam Lally wrote:
You don't need a tool to do this. Just go to JIRA and click the
"Release Notes" link at the top.
I opened an issue UIMA-254 a while back that says we need release
notes, and that JIRA can generate them.
I agree we Adam, for creating release notes, we can also use JIRA, we
don't need to use my tool.
My tool is helpful when you need to to know which issues were fixed
for levels during the test for example, or when having branches/tags;
what was fixed based on such a tag/branch.
Further, I played around with the JIRA release notes generation and
figured out that the release notes are created based on the the
"Fixed Version" attribute of an issue.
So if that field contains no data, the issue is not added to the
release notes of the selected release. :-) We have about 50 fixed
issues that have no version specified in the
"Fixed Version" field. So some of them are certainly issues from the
migration of UIMA to Apache and it doesn't matter if they appear in
the release notes or not. But others, I think should appear.
So my suggestion is, that the assignee reopens these issues that
should appear in the release notes and "fixed them again" with adding
the "Fixed Version" attribute correctly.
What do others think?
+1 to marking things fixed in 2.1 as fixed in 2.1.
Did your comment mean to imply that for things that are not real bug
fixes but rather are just porting, we should mark as "blank"? I don't
think I like that idea.
Here's a couple of thoughts. My (slight, easy to talk me out of it)
preference is to just go ahead and mark everything in Jira that is
included in 2.1, as being included in 2.1. Yes, that will be a big
list. But we can say why it's so big.
Alternatively, we could create another release number - call it
2.1-migration-to-Apache for instance, and mark those things that we
think should not be in the 2.1 "fix" list, as being in this other
list. That way, we're clearly documenting things, making it easier
for the reviewers (and future users) to understand what's going on.
-Marshall
So in this case, I would mark all issues that are currently fixed as
fixed in 2.1. I'm fine with that. I don't like the idea creating another
release. I think we cannot differentiate all issues clearly into two
releases.
-- Michael.
