Eclipse Linux Tools 3.1.0 Release Review

Type: 
Release
State: 
Successful
End Date of the Review Period: 

Reviews run for a minimum of one week. The outcome of the review is decided on this date. This is the last day to make comments or ask questions about this review.

Wednesday, October 29, 2014
Release: 

3.1.0

Description: 

The 3.1.0 release of Linux Tools is a minor release which will be contributed as part of Luna SR1.  The Linux Tools project normally offers minor releases in the SR1 and SR2 release periods.  This minor release contains a few enhancements such as: vastly greater performance for Libhover devhelp start-up, the addition of offering automatic rebuild for projects using gcov/gprof that have not been compiled properly, SystemTap graphing and job cancellation enhancments, and LTTng additions including live tracing support and support for reading libpcap traces.

API Certification: 

The project leadership certifies that the APIs in this release are "Eclipse Quality".

Architectural Issues: 

Ongoing work to integrate with tracing and profiling toolkits will enable us to have more extensible frameworks with exemplary implementations.
Despite being user-focused, we have a few components which provide extension points:
   our profiling tool framework whose use is demonstrated by all of our profiling integration plug-ins: Gcov, Gprof, Perf, OProfile and Valgrind
   our ChangeLog plugin which allows for extensible parsers, formatters, and editors. The extensibility of formatters is demonstrated by our RPM .spec editor
   our libhover component. This plugin provides an extension point that defines a common documentation format for C library hover help
   our LTTng component. This plugin provides an extension point to integrate any type of trace and an extension point for producing UML2 sequence diagrams from traces

Usability Details: 

Our project aims to conform to the Eclipse user interface guidelines.
 All of our user interface components support keyboard navigation.
 We support interactivity of our Valgrind charts and intend on further increasing our accessibility.
 All of our strings are externalized but we currently have no language packs
 Our strings are registered in Babel for use by translators

End of Life: 

We have no end-of-life issues to discuss at this time.

Standards: 

Our project conforms to the following standards, some of which are ad-hoc and some which are more well-defined:
  Fedora RPM packaging guidelines
    http://fedoraproject.org/wiki/Packaging/Guidelines
  Informal conventions around use of the GNU Autotools
  GNU ChangeLog formatting
    http://www.gnu.org/prep/standards/html_node/Style-of-Change-Logs.html#St...
 LTTng trace format
   http://lttng.org

Communities: 

Our project has a strong relationship with the various Linux distributions (Fedora, Mandriva, Debian, Ubuntu, etc.) with many using our eclipse-build project's output for their Eclipse SDK packages
The majority of our project's interactions occur on IRC (#eclipse-linux) and our mailing list (linuxtools-dev@eclipse.org)
We have a centralized update site and use eclipse.org bugzilla for all of our planning and bug tracking
We make use of our newsgroup for user feedback
Our project members often speak at conferences such as EclipseCon, the Red Hat Summit, etc.
Our team members maintain the following blogs:
   http://akurtakov.blogspot.com/ (part of Planet Eclipse)
We interact often with the CDT project and make use of the GEF and CDT projects
We are growing our community of adopters