[jbosstools-dev] JIRA maintenance -- moving issues from CR1 -> Beta2

[Nick Boldt]

49 issues now marked resolved for JBT 4.0.0.Beta2:

https://issues.jboss.org/secure/IssueNavigator!executeAdvanced.jspa?jqlQuery=project+in+%28JBIDE%2CTOOLSDOC%29+AND+fixVersion+in+%28%224.0.0.Beta2%22%29+AND+resolution+not+in+%28Unresolved%29&runQuery=true&clear=true

4 issues now marked resolved for JBDS 6.0.0.Beta2:

https://issues.jboss.org/secure/IssueNavigator!executeAdvanced.jspa?jqlQuery=project+in+%28JBDS%29+AND+fixVersion+in+%28%226.0.0.Beta2%22%29+AND+resolution+not+in+%28Unresolved%29&runQuery=true&clear=true

19 unresolved issues for Beta1 which need to be re-targeted to Beta2 or 
CR1, or closed as part of today's Beta1 release:

https://issues.jboss.org/secure/IssueNavigator!executeAdvanced.jspa?jqlQuery=%28project+in+%28JBIDE%2CTOOLSDOC%29+AND+fixVersion+in+%28%224.0.0.Beta1%22%29+or+project+in+%28JBDS%29+AND+fixVersion+in+%28%226.0.0.Beta1%22%29%29+AND+resolution+in+%28Unresolved%29&runQuery=true&clear=true

Cheers,

Nick

On 11/01/2012 11:55 AM, Nick Boldt wrote:
> Going to do this in JBIDE JIRA:
>
> 1. rename CR1 -> Beta2
>
> 2. create replacement CR1 version
>
> 3. move unresolved in Beta2 BACK to CR1, so they can be manually triaged
> into Beta2 (if required). This means all the Closed/Resolved issues
> previously set for CR1 will now be set to Beta2, and all the Unresolved
> issues will be set for CR1.
>
> 4. Max/Denis/component leads to manually review unresolved issues set
> for in Beta1 to decide which should move to Beta2 or CR1
>
> 5. Max/Denis/component leads to manually review unresolved issues set
> for in CR1 to decide which should move to Beta2
>
> Repeat for JBDS JIRA.
>

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com