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.
The project leadership certifies that the APIs in this release are "Eclipse Quality".
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
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
Our releases thus far have been well-received and at present have satisfied users. This 3.0 release will hopefully continue to grow our base of satisfied users. Our work integrating native profiling tools like LTTng, perf, OProfile, and Valgrind has been introduced to excited audiences. We aim to improve the power of these tools within the IDE making them easier to use and to support additional functionality that is provided via the command line. Developers making use of our tools will be able to focus on their own projects and not on setting up the underlying tools.
We have no end-of-life issues to discuss at this time.
Our project conforms to the following standards, some of which are ad-hoc and some which are more well-defined:
Fedora RPM packaging guidelines
Informal conventions around use of the GNU Autotools
GNU ChangeLog formatting
LTTng trace format
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 (email@example.com)
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