[jbosstools-issues] [JBoss JIRA] (TOOLSDOC-705) JBDS 9.1 Beta2: Release Notes

[Martin Malina (JIRA)]

    [ https://issues.jboss.org/browse/TOOLSDOC-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13157553#comment-13157553 ] 

Martin Malina commented on TOOLSDOC-705:
----------------------------------------

Hi [~mhusnain], I have comments about the queries.
4.1. Resolved Issues
The query you include shows 64 issues total:
{code}
(project in (JBDS) AND affectedVersion <= 9.1.0.Beta2 AND fixVersion in (9.1.0.Beta2)) OR (project in (JBIDE) AND affectedVersion <= 4.3.1.Beta2 AND fixVersion in (4.3.1.Beta2)) AND type in (Bug) AND resolution in (Done)
{code}
I wonder why we have the affectedVersion there. Do you know? Without it, we have 75 issues. I think the idea was to exclude issues that never appeared in a previous versions - for example when there is a new functionality in Beta2 and there is a bug recognized right away and fixed still in Beta2 before anybody had a chance to even see this bug. But on the other hand, this also misses issues without affectedVersion set at all which in this case is 7 issues out of those 75. So I think it's better to remove the affectedVersion constraints there.

4.2. Known Issues
You decided to remove "OR resolution in (Done)", but there was a reason for that. There were two parts of the query - the first part was bugs, that are still open at the time of the search - in the past we limited this only to bugs with older affectedVersion because newer bugs might not be relevant. But I'm fine with removing this.
The second part is bugs, that are already resolved at the time of the search, but were fixed later on, so for this release, they were present. For example let's say it is March and JBDS 9.1.0.GA is already out. You decide to check Beta2 Release Notes. And in the known issues query, you want to see which bugs were still present in Beta2. Let's say there is a bug JBDS-9999 that was fixed in 9.1.0.CR1. You still want to see this bug in Beta2 known issues query. That's why you have: resolution in (Done) AND fixVersion > "9.1.0.Beta2" - this was a bug that is now fixed, but was still present in Beta2. So I think this is still reasonable to have there.
So I would suggest this query:
{code}
(project in (JBDS) AND (affectedVersion <= "9.1.0.Beta2" OR affectedVersion is EMPTY) AND (resolution in (Unresolved) OR resolution in (Done) AND fixVersion > "9.1.0.Beta2") OR project in (JBIDE) AND (affectedVersion <= 
"4.3.1.Beta2" OR affectedVersion is EMPTY) AND (resolution in (Unresolved) OR resolution in (Done) AND fixVersion > "4.3.1.Beta2")) AND type in (Bug)
{code}
I believe this is the last query that you suggested before you dropped the resolved jiras from the query.
What do you think?

> JBDS 9.1 Beta2: Release Notes
> -----------------------------
>
>                 Key: TOOLSDOC-705
>                 URL: https://issues.jboss.org/browse/TOOLSDOC-705
>             Project: Documentation for JBoss Tools and Developer Studio
>          Issue Type: Bug
>            Reporter: Misha Ali
>            Assignee: Martin Malina
>
> Create new Beta2 release notes, fix the script and update the relevant details.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)