Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
CDT/summitecon2015
Contents
CDT/Linux Tools/PTP/Trace Compass Summit at EclipseCon 2015
A one-day CDT/Linux Tools/PTP/Trace Compass Summit will be held at EclipseCon 2015 in San Francisco, CA, on Monday March 9th, 2015. This summit is open to registered attendees of EclipseCon. Please register here. It is an informal gathering of committers and contributors of the mentioned communities to discuss project direction, on-going work, proposed changes and enhancements, and any other topic of interest to the participants. It will be followed on the Tuesday by a CDT Theme Day of 7 official EclipseCon presentations related to these projects.
The below agenda may evolve as proposed topics are added and attendees sign-up.
To help structure the summit, please:
- add your name to the attendees section below
- add agenda items you would like to see discussed
Sponsors
Agenda
9:00-9:30
- Welcome and agenda adjustment
9:30-12:00
- Move to Java 8?
- Recommended changes to make to CDT when on Java 8
- Lambdas
- Would be valuable to DSF
- Would need to adapt APIs to work with Lambda
- Existing code could remain the same but new code could then use Lambdas
- Readability? Experience shows it should be improved
- Error handling for RequestMonitor class would be difficult, may not be a good fit.
- Error handling could be done by having one method taking an error handler and a success handlers
- Default methods
- No more IMyInterface2 pattern
- We expect binary compatibility to be maintained in this case
- We would not remove existing IMyInterface2 to be nice to extenders but we could deprecate (some) of them.
- Lambdas
- API tooling support (e.g., handling of default methods)
- We don't know. We'll need to check early. If not, we need to revisit the use of default methods.
- Recommended changes to make to CDT when on Java 8
- Doing a 9.0 release to allow breaking APIs
- Must make a clear decision to allow work to begin ASAP
- Yes. We must confirm with the list.
- Announce in latest N&N.
- Create branch early.
- Branching strategy. How do we begin work early while allowing SR releases from master?
- Need a branch: APIBreak_9_0
- Keep *merging* master into APIBreak_9_0 to keep the two aligned
- Right after MarsSR2 (CDT 8.9) we bring APIBreak_9_0 to master, or even rename APIBreak_9_0 to master
- List of changes that should be looked at: https://wiki.eclipse.org/CDT/APIBreakages
- Must make a clear decision to allow work to begin ASAP
- Oomph demo: setting up Eclipse for CDT development in a few clicks
- https://wiki.eclipse.org/Getting_started_with_CDT_development#Using_Oomph
- Eclipse installer that has been setup to handle CDT
- Will do entire CDT setup for contribution, including API baseline
- Setup file is at org.eclipse.cdt/releng/CDT.setup
- The Oomph catalogue points to the CDT repo for the file so all changes propagate from CDT automatically
- Existing setup file can be extended for a local team
- Existing git clone of CDT can be re-used when triggering a new installation through Oomph
- Marc-Andre gave a nice little demo. Super easy to use!
- Other projects can do the same pretty easily
- We should add Gerrit push automatically
- Standalone Debugger RCP: Discussions and/or demo.
- Product on top of the Standalone debugger
- We will add it somehow to the CDT project pages, CDT downloads page
- Bugzilla backlog
- Entries should be marked as Enhancement when not a bug
- Suggestions for Enhancement and some bug fixes could be done by the person writing the bug or other contributors
- How do we motivate people to fix bugs? We could try the approach of the "Mars great fix contest"
- Point potential contributor immediately to CDT Oomph setup to get them started quickly
- Improve tools that help discover code (e.g., plugin spy, code references)
12:00-13:00
- Lunch provided by EclipseCon
13:00-15:00
- org.eclipse.remote and CDT
- TM Terminals
- Launchbar
- Toolchains: LLDB, Clang, Visual Studio
- Content assist setting to completion
- New project wizard
- What shall we do with our current CDT Launches?
- What's new in CDT?
15:00-15:15
- Break
15:15-16:30
- Bugzilla "mentoring" tag
- How do we tell our users about cool features?
- FindBugs, Sonar and general CDT quality
- Next gathering: hackathon?
- Conclusion
16:30-17:30
- Happy Hour (Exhibit Area)
18:00
- Summit dinner free of charge for attendees at the Elephant Bar restaurant.
Tentative Attendees
- Marc Khouzam - Ericsson
- Community, Debug, Multicore, Visualizer, Tracing
- William Riley - Renesas
- Debug (Embedded), Multicore, Tracing, UX, Codan
- Marc-Andre Laperle - Ericsson
- Tracing, Debug, Community, Editor, Refactoring, Codan, Build, UX
- Andrew McLachlan - Analog Devices
- Tracing and Debug
- Srinivas Gudla - Xilinx
- Tracing, Visualizer, Multicore and Debug
- Sergey Prigogin - Google
- Parser, Indexer, Refactoring, Codan
- Doug Schaefer - QNX/BlackBerry
- Everything. Mainly Remote Launching, Qt, UX.
- Greg Watson - IBM
- Remoteness and target management
- Jeff Johnston - Red Hat
- Remote Launching, Debug
- Alena Laskavaia - QNX/Blackberry
- UX, Launch, Debug, Codan, Build
- Vladimir Prus - Mentor Graphics
- Everything
- Wyatt Spear - University of Oregon
- Performance analysis, tool integration
- Mohamed Azab - Mentor Graphics
- UX, Multicore, Codan, Parser, Indexer.
- Appa Rao Nali - Xilinx
- Tracing, Visualizer, Multicore Debug
- Yufen Kuo - Cavium
- Tracing, Remote Profiling, Remote Launching
- Jesper Eskilson - IAR Systems
- Most things
- Roland Grunberg - Red Hat
- Linux Tools Project
- Martha Benitez - Red Hat