[jbosstools-dev] ACTION REQUIRED: JBoss Tools + Developer Studio triage time

[nboldt at redhat.com]

As the current sprint 'devex #149 May 2018' draws to a close, it is time 
to review your unresolved issues! 

Some may be done (or will be done soon), but the JIRA(s) need resolution.

Others may need to be pushed to the next milestone (4.6.0.AM3 + 12.0.0.AM3), 
to a future .x release, or LATER.

All unresolved issues for 4.6.0.AM2 + 12.0.0.AM2:

https://issues.jboss.org/issues/?jql=(project%20in%20(JBDS)%20AND%20fixVersion%20%3D%2012.0.0.AM2%20OR%20project%20in%20(JBIDE)%20AND%20fixVersion%20%3D%204.6.0.AM2)%20AND%20resolution%20%3D%20null

All *YOUR* unresolved issues for 4.6.0.AM2 + 12.0.0.AM2:

https://issues.jboss.org/issues/?jql=(project%20in%20(JBDS)%20AND%20fixVersion%20%3D%2012.0.0.AM2%20OR%20project%20in%20(JBIDE)%20AND%20fixVersion%20%3D%204.6.0.AM2)%20AND%20resolution%20%3D%20null%20and%20assignee%20%3D%20currentUser()

Once created, you can also begin scheduling your work for the upcoming 
sprint, 'devex #150 June 2018'. 

Triage tips:

* blocker/critical issues: make these your priority work for the next sprint:
  move to next version & assign to the next sprint

* other issues that WILL be done in the next sprint: 
  move to next version & assign to the forthcoming sprint, but lower down

* non-blocker & non-critical issues not for the next sprint: 
  move to .x (or LATER)