ACTION REQUIRED: JBT 4.3.0.CR1 triage
by Alexey Kazakov
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
<https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20resolu...>
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%20resolu...
*Hibernate, 14 *(plus 6 Forge issues below as a bonus for Koen ;-) *:*
https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20compon...
*
**Server + runtime detection, 12:*
https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20resolu...
*
**Webservies, 10:*
https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20compon...
*Docker, 8:*
https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20compon...
*Easymport, 8:*
https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20compon...
*Arquillian, 7:*
https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20compon...
*
**Central, 7:*
https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20compon...
*
**Forge, 6:*
https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20compon...
*
**Freemarker, 6:*
https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20compon...
*VPE, 6:*
https://issues.jboss.org/issues/?jql=project%20%3D%20JBIDE%20AND%20resolu...
Thank you!
9 years, 3 months
Planning for Eclipse Neon (2016-2017)
by Nick Boldt
Just a quick heads up re: next year's Eclipse Simultaneous Release.
The Eclipse Planning Council is working on a plan to do 4 Neon
releases: 1 main one in June 2016 followed by 3 updates in September
2016, (early) December 2016, and March 2017. This is still being
finalized.
Projects will be able to join the train for any of these milestones,
not just the main one in June. Goal is to provide easier access to
joining the train and support more projects wanting to do updates at
more points throughout the year.
For Mars, the plan is to do the usual 1 main release (completed back
in June 2015) followed by 2 update releases at the usual dates:
September and February. For Luna these were called "Service Releases"
but from Mars onward they are "Update Releases", in that new features,
new projects, & minor updates are now allowed.
Gone is the annual monolith; long live quarterly releases!
More info: https://wiki.eclipse.org/Planning_Council/September_02_2015
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
9 years, 3 months