Hi all,
As you know we have less than 4 weeks before the code freeze for
CR1.
And we still have a lot of unresolved issues targeted for CR1: 185
issues in https://issues.jboss.org/browse/JBIDE
I know it happens every time we are approaching a release. We just
wait the next code freeze than move all unresolved issues to the
next version. It really doesn't help to see the status of
development.
Having a clean JIRA which reflects reality is a very important thing
for such a big team as ours.
So please, give some love to your component in JIRA and move
everything which is not blocker/critical for CR1/GA (and you are not
sure if you have time to fix in next 3-4 weeks) out of 4.3.0 scope now.
Don't wait for the code freeze or personal ping.
So, the CR1/Final JIRA should have only:
- blocker/critical issues
- major/minor issues you are sure you will fix safely during next
3-4 weeks.
If something is blocker/critical but you can't fix it before the
code freeze, please speak up now!
Here is the list of components with the biggest numbers of
unresolved issues (I didn't include OpenShift with 52 issues
because OS is a special case and it's kinda expected):
Build, 24 issues:
https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20in%20(4.3.0.CR1%2C%204.3.0.Final)%20AND%20component%20%3D%20build%20ORDER%20BY%20priority%20DESC
Hibernate, 14 (plus 6 Forge issues below as a bonus for Koen
;-) :
https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20component%20%3D%20hibernate%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%204.3.0.CR1%20ORDER%20BY%20priority%20DESC
Server + runtime detection, 12:
https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%204.3.0.CR1%20AND%20component%20in%20(runtime-detection%2C%20server)%20ORDER%20BY%20priority%20DESC
Webservies, 10:
https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20component%20%3D%20webservices%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%204.3.0.CR1%20ORDER%20BY%20priority%20DESC
Docker, 8:
https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20component%20%3D%20docker%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%204.3.0.CR1%20ORDER%20BY%20priority%20DESC
Easymport, 8:
https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20component%20%3D%20easymport%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%204.3.0.CR1%20ORDER%20BY%20priority%20DESC
Arquillian, 7:
https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20component%20%3D%20arquillian%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%204.3.0.CR1%20ORDER%20BY%20priority%20DESC
Central, 7:
https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20component%20%3D%20central%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%204.3.0.CR1%20ORDER%20BY%20priority%20DESC
Forge, 6:
https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20component%20%3D%20forge%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%204.3.0.CR1%20ORDER%20BY%20priority%20DESC
Freemarker, 6:
https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20component%20%3D%20freemarker%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%204.3.0.CR1%20ORDER%20BY%20priority%20DESC
VPE, 6:
https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%204.3.0.CR1%20AND%20component%20in%20(visual-page-editor-core%2C%20visual-page-editor-templates)%20ORDER%20BY%20priority%20DESC
Thank you!