|[tools-pmc] PTP Indigo Release Review|
Please approve the PTP docuware below for the review.
PTP Indigo Release Review (Including Photran Subproject)
Updated Eclipse package support
- Eclipse 3.7
- CDT 8.0
- RSE 3.3
- New resource manager framework
- XML based resource manager configuration
- Scalable monitoring based on LLview
Remote development tools (RDT):
- Remote synchronized projects
- Many fixes and improvements to remote indexing
Parallel Language Development Tools (PLDT)
- Less intrusive MPI/OpenMP preferences
- More accurate location of artifacts including within macro expansions
External tools framework (ETFw)
- ETFw now provides combo-box UI components.
- Improvements to general-purpose tool workflow support
- Numerous bugfixes
Photran (Fortran development tools)
- Code templates
- Correct indentation command
- Editor improvements
- 19 new refactorings
- Bug fixes
New & Noteworthy
- PTP interfaces are Eclipse quality
- API tooling has been enabled on all plugins
- Version numbers have been incremented where appropriate
- Internal/experimental APIs marked as such
- 156 bugs opened
- 109 bugs resolved/closed
- 47 new/open bugs
RC1 - Build Tue, May 17 - Release Wed, May 20
RC2 - Build Tue, May 24 - Release Wed, May 27
RC3 - Build Tue, May 31 - Release Wed, June 3
RC4 - Build Tue, June 7 - Release Wed, June 10
This release has been developed using open, transparent, and inclusive processes.
This release has followed its charter principles.
The PTP project makes appropriate use of
- Mailing lists (ptp-announce@xxxxxxxxxxx, ptp-dev@xxxxxxxxxxx, ptp-user@xxxxxxxxxxx, photran@xxxxxxxxxxx, photran-dev@xxxxxxxxxxx)
- Regular, monthly, conference calls
- Wiki (http://wiki.eclipse.org/PTP)
There were four committer elections during the 5.0 release cycle:
- Tu Hong Jun
- Alan Humphrey
- John Liu
- John Eblen
- Wolfgang Frings
Monthly developer meetings held every second Tuesday of the month
Annual birds-of-a-feather session at the SC Conference
All plugins contain appropriate about and license files.
All contributions (code, documentation, images, etc) have been committed by individuals who are either Members of the Foundation, or have signed the appropriate Committer Agreement; in either case, these are individuals who have signed, and are abiding by, the Eclipse IP Policy.
Major contributions have followed due diligence process.
All non-committer code contributions, including third-party libraries, have been documented in the release and reviewed by the Foundation's legal staff.
All contribution questionnaires have been completed.
IP Log available at
Project plan available at:
The communication channel for the review should be the following mailing list:
Back to the top