1 / 22

Eclipse BIRT 2.2 Release Review May 30, 2007

Eclipse BIRT 2.2 Release Review May 30, 2007. DRAFT 1. Eclipse BIRT PMC. Introduction: BIRT 2.2 Release Review. BIRT 2.2 is targeted for availability June 29, 2007 Based on Eclipse Platform 3.3 Part of Europa Simultaneous Release Major Milestone History 1.0, Jun 2005; 1.0.1, Jul 2005

keelie-barron
Télécharger la présentation

Eclipse BIRT 2.2 Release Review May 30, 2007

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Eclipse BIRT 2.2 Release Review May 30, 2007 DRAFT 1 Eclipse BIRT PMC

  2. Introduction: BIRT 2.2 Release Review • BIRT 2.2 is targeted for availability June 29, 2007 • Based on Eclipse Platform 3.3 • Part of Europa Simultaneous Release • Major Milestone History • 1.0, Jun 2005; 1.0.1, Jul 2005 • 2.0, Jan 2006; 2.0.1, Feb 2006 • 2.1, Jun 2007; 2.1.1 Sep, 2006; 2.1.2 Feb 2007 • Release alignment • “Major” release designation determined by feature set • Summer releases will be aligned with Eclipse release train

  3. Features: BIRT 2.2 Requirements Process • Requirements gathered from multiple sources: • Enhancement requests already entered in Bugzilla • Discussions in BIRT newsgroup • Innovation/experience from within the BIRT project team • Requirements captured in Bugzilla • Community encouraged to enter all enhancements into Bugzilla for planning and tracking • Candidate projects identified and listed on BIRT Wiki • BIRT Project Specifications (BPS) created to define scope and encourage discussion and feedback • BIRT 2.2 Plan developed and published on Eclipse.org

  4. Features: Summary of BIRT 2.2 Objectives & Themes • Integrate and provide BIRT as part of the Europa Simultaneous Release • Support use of BIRT in a wide range of Eclipse 3.3 applications • Ensures BIRT technology is easily accessible to Eclipse 3.3 community • Specific additional features can be grouped into broad categories • Dynamic crosstab support based on multi-dimensional OLAP engine • Support for Eclipse 3.3 (tested with Europa components) • Data access/Contributions to DTP (e.g. Web Services data source; dynamic connection profiles; enhanced runtime API) • Output formats (e.g. Performancesoft, MS Excel, MS Word, MS PowerPoint output) • Formatting (e.g. Reference external CSS; Table of Contents Formatting) • Deployment and Integration (e.g. components to easily deploy BIRT in a web application) • Parameters (e.g. default values; optional parameters) • Charts (e.g. New chart types, including Gantt; Smart Labels; improved scaling/grouping) • Usability improvements (e.g. Chart Designer; XML Editor; Extensibility) • Scripting (e.g. improved access to documentation) • Use of Eclipse 3.2 features (e.g. new Property Editor; improved Project Explorer) • Incorporate Eclipse Themes & Priorities where applicable For Details, refer to BIRT 2.2 Release Plan and Bugzilla

  5. Non-Code Aspects: Documentation & Examples • BIRT 2.2 download includes online documentation • Created by professional technical writers • Tutorials and examples available on www.eclipse.org/birt • How-To recorded demos • Articles on common BIRT usage scenarios • Examples of common reports • Example code snippets • BIRT includes an embedded Derby sample database • Easy to learn how to use BIRT with tutorials and examples • Standard SQL data that can easily be loaded into other DBs • New & Noteworthy documents • Have been created for Milestone releases • Comprehensive BIRT 2.2 N&N will be created for final 2.2 release

  6. Non-Code Aspects: Internationalization & Localization <<This Slide Needs Final Confirmation from I18N Team>><<Ideally Need to Include Localized Language Pack List>> • BIRT uses Eclipse and Java localization/internationalization infrastructure • Report architecture enables easy localization of labels/text in actual reports • BIRT is tested for 23 locales/languages: • Currently right to left (bi-directional) support in PDF output is limited • 9 group 1 languages • German • Spanish • French • Italian • Japanese • Korean • Brazilian Portuguese • Traditional Chinese • Simplified Chinese • 4 group 2 CEMA languages • Czech • Hungarian • Polish • Russian • 8 group 2a additional languages • Danish • Dutch • Finnish • Greek • Norwegian • Portuguese • Swedish • Turkish • 2 group Bi-Directional languages • Arabic • Hebrew

  7. APIs: Overview • Intention is for new APIs to go through at least one release of Provisional status to allow for feedback • Community feedback on APIs prompted a number of enhancements and improvements in BIRT 2.2 • Goal for BIRT 2.2 is to support BIRT 2.1 APIs that are in use by the community. Known exceptions are: • BIRT 2.1 or earlier APIs that did not work • BIRT 2.1 APIs that have transitioned to DTP project • Any compatibility issues should be reported as defects and we will work to address them where possible

  8. APIs: Status API Contract Compatibility: BIRT 2.2 is upwards contract-compatible with BIRT 1.x; 2.0.x and 2.1.x to the greatest extent possible. All incompatibility exceptions will be documented. Downward contract compatibility is not supported. There is no guarantee that compliance with BIRT 2.2 APIs will ensure compliance with BIRT 1.x; 2.0.x; 2.1.x APIs. Refer to general Eclipse document on Evolving APIs for a discussion of the kinds of API changes that maintain contract compatibility.

  9. End of Life Issues • No features or APIs are moving into End of Life in this release

  10. Architectural Items • No changes from BIRT 2.1

  11. Bugzilla Statistics • Dedicated professional QA team testing BIRT • Strong participation in testing from Community • All bugs are tracked through Bugzilla • Release Exit Criteria • Zero outstanding Critical defects • Zero outstanding Major defects • 100% test attempt / pass • All automated tests/JUnit tests are in CVS

  12. Bugzilla Statistics Note: NEW and ASSIGNED for Target Milestone 2.2.0 are still candidates for 2.2 but will likely move to 2.2.1 (88 bugs fall into this category) Bug statistics as of 4:30 pm Pacific, May 30, 2007

  13. Code Statistics Statistics as of May 30, 2007. Statistics do not include 3rd party open source code and binaries. Line count does not include comments and blank lines.

  14. Standards (same as BIRT 1.0.x, 2.0.x, 2.1.x) • BIRT is designed to work in a standards-based environment • Eclipse plug-ins for design-time activities • General Java class libraries for deployment • Ability to render reports as HTML pages for output • Example deployment implementation for Apache Tomcat • BIRT uses JavaScript for scripting (Mozilla Rhino engine) • Conforms to ECMA-262 standard • Reference: http://www.mozilla.org/js/

  15. Schedule • BIRT 2.2 adopted Eclipse Europa Simultaneous Release Schedule

  16. Process • 79 committers for the Eclipse BIRT project • Committer elections and removals have followed charter principles • Continuing to recruit additional contributor organizations/individuals • Open and inclusive release planning and tracking processes • Bugzilla used to request and track all defects and enhancements • Leveraging other open source in the project where possible • Examples: Rhino; Flute; Tomcat; Derby • All contributions made directly to Eclipse CVS • Nightly, stable, and release builds available to the community • Project specific process details are posted on project web site • http://www.eclipse.org/birt/phoenix/project/ • Weekly PMC meeting with minutes distributed to community

  17. Community • Open communications via 6 BIRT mailing lists and 1 newsgroup • Project activities communicated via mailing lists for PMC/general • One mailing list for each sub-project • Plus low-noise news only mailing list • Newsgroup is very active • 19,752 postings as of May 30, 2007 • Many how-to questions and discussions • Typically same day responses from BIRT team • Have adjusted projects in response to newsgroup feedback • Dedicated resources generating content for BIRT community at Eclipse.org • BIRT project pages • BIRT Wiki • Coordination/cooperation between other open source projects • TPTP incorporates BIRT functionality • BIRT Committers also work on DTP project; DTP is key component of BIRT

  18. Community • Articles and Technical Content Placement • 11 significant articles published in last 12 months • See http://wiki.eclipse.org/index.php/Articles(BIRT) for details • Conferences and User Groups • EclipseCon 2007, March 2007: 11 talks/tutorials on BIRT project technology • Presented on BIRT at over 10 other conferences during last 12 moths • Blogging • BIRT World: http://birtworld.blogspot.com • Promoting BIRT on many other sites such as TheServerSide, JavaLobby and EclipseZone • Books • Two books are published by Addison-Wesley on BIRT: • BIRT: A Field Guide to Reporting • Integrating and Extending BIRT • Both can be pre-ordered from Amazon or your favorite retailer

  19. Intellectual Property <<Need Status of Source Scan from EMO>> • Accepting Contributions (In-Bound Licensing) • All BIRT code provided under Eclipse Public License (EPL) • BIRT downloads include only 3rd party (non-EPL) components approved by EMO • Licensing Contributions (Out-Bound Licensing) • BIRT 2.2 provided under EPL • About files and license files are complete and correct • Due Diligence and Record Keeping • All BIRT Committers completed Committer Agreement & approved by PMC/EMO • PMC maintains list of all 3rd-party (non-EPL) components used by BIRT • EMO source scan and due diligence is <<in progress or completed?>> • BIRT 2.2 will not be released until this is complete with a positive result • Project Log maintained by the PMC Eclipse Foundation IP Policy: http://www.eclipse.org/org/documents/Eclipse%20IP%20Policy2003_12_03%20Final.pdf

  20. Intellectual Property Cleanliness <<DRAFT. Project Log is being updated and this slide will be updated accordingly>> • The following significant and third party contributions have been reviewed by Eclipse Legal • Rhino 1.6R1 • Apache Derby 10.1.2.1 • Jakarta Commons CLI 1.0 • JTidy R7 • Simple API for CSS 1.3 • Flute 1.3 • Commons codec1.3 • Xerces2 Java Parser 2.8 • Apache Axis 1.3 • Prototype.js 1.4.0 • Batik 1.6 • iText 1.5.2 • Project log complete and in the process of being reviewed by Eclipse Legal • The URL is http://www.eclipse.org/birt/project-info/ProjectLog.html

  21. Project Plan • BIRT 2.2 scheduled for Jun 29, 2007 • Based on and supports Eclipse 3.3 • Part of Eclipse Europa Simultaneous Release • Does not support Eclipse 3.2.x or earlier • BIRT 2.2.1 tentatively scheduled for Q4 2007 • Maintenance release • Ideally, synchronized and tested with Eclipse Platform 3.3.1 • Exact date pending data on planned date for Eclipse Platform 3.3.1 • BIRT release tentatively targeted for Jun 2008 • Synchronized with Eclipse Ganymede Simultaneous Release • Feature set and planning will determine release designation • Detailed planning and release designation TBD

  22. Thanks and… Feedback, Feedback, Feedback! • Please provide us with your feedback, requirements, issues • Submit enhancement requests / defects in Bugzilla https://bugs.eclipse.org/bugs/enter_bug.cgi?product=BIRT • Submit questions / issues in the BIRT Newsgroup: news://news.eclipse.org/eclipse.birt • Engage with the PMC to contribute: birt-pmc@eclipse.org or individual PMC members (see http://www.eclipse.org/birt/phoenix/project/pmc.php)

More Related