Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [che-dev] Eclipse Che 3.10.0 Features
My general take for release planning through the 3.x train is that we should only commit to one feature for a release, and make that the decision point for deciding when we release or not.  This will keep the release necessarily small and allow us to release more frequently.  If there are other features that are completed at that point in time, then they can also be merged in for inclusion.  

But by setting such a large release with so many issues, the tracking becomes much more difficult, and our ability to ship is tied to the longest critical path feature, more than anything else.

So, for 3.10, I would say that svn / git related features are the must have, and that is the only thing that is mandatory (other than critical + blocker bugs).  And for everything else, it's floating as no fixVersion, and dynamically added in if completed in time.  

And by only targeting svn / git features, we could be in a position to release in 1-2 weeks if we so chose.

Tyler

Tyler Jewell | CEO | tyler@​codenvy.​com | 9​78​.8​84​.53​55


On Thu, Apr 23, 2015 at 10:31 PM, Gennady Azarenkov <gazarenkov@xxxxxxxxxxx> wrote:
It is important to finish 2,3,4 it was postponed only in order to make 3.9 ASAP.

I would say 4 is also important and has to be started ASAP, not sure if will be finished for 3.10

Do you have in mind some particular urgent requirements?


Gennady Azarenkov - CTO @ codenvy.com


On Fri, Apr 24, 2015 at 1:04 AM, Tyler Jewell <tyler@xxxxxxxxxxx> wrote:
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

Tyler Jewell | CEO | tyler@​codenvy.​com | 9​78​.8​84​.53​55


On Thu, Apr 23, 2015 at 6:53 AM, Dmitry Kuleshov <dkuleshov@xxxxxxxxxxx> wrote:
Hi,

Soon we will start work on 3.10.0 version. You can see currently planned features here: https://wiki.eclipse.org/Che/Roadmap

Shortly they are:
  • Have all project type extensions support creating a new project without setting mandatory parameters
  • New default flows during login
  • Horizontal splitter to enable console + terminal view side by side
  • Restoring state of project explorer from last visit
  • Taking git committer name and email from user preferences
  • Using EventService or alternative mechanism for filling Item(s)' Properties retrieved with ProjectService dynamically
  • Restoring the state of previous session when enter IDE
  • One war assembly for local (SDK) IDE
  • Svn merge action
  • Subversion commands in Project Explorer context menu
  • Observing files changes before commit
  • Silent Build Option
The development of a new version is not started yet so the list is not final and I would like to discuss if the it is ok for you or there is something we should add on your opinion. Please feel free to express your ideas on any feature you think should be in 3.10.0.

In the end of the discussion I will summarize everything and update the wiki with the final features plan.

With regards,
Dmitry

_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/che-dev



_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/che-dev



_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/che-dev


Back to the top