In looking at 3.10, it feels like we have too many things in a release. Granted, all of these things are smaller scope and they are in different sub-systems, but we have talked about trying to narrow down major releases to ~50 issues resolved instead of the monster 300 that we are looking at with 3.9. Additionally, we are likely to start seeing additional questions / points arise from ecosystem adopters and Codenvy OEMs - as the number of deals there have started to escalate quickly. So, it may make sense to schedule less into a release and allow us to leave more room for handling urgent requirements from SAP, WSO2, YD, Huawei and others.
My proposal to move all of hte following to 3.11:
1. Empty constructor for all PT
2. Restoring state of IDE from previous session
3. Restoring state of project explorer
4. New default flows in login
5. One WAR assembly
This effectively leads git / svn commands, improvements to multi-runner, and a series of additional requirements from Codenvy around improvements to metering.
Separately:
1. We have a PR from Sun Tan on packaging the Docker plug-in with SDK. Should we consider this?
2. We have a PR from WSO2 on the chromium packaging. Should we consider this?
Of course, all critical + blocker IDE bugs will be targeted for extermination.
Tyler