1 / 3

Yearly Cadence for XLIFF 2.x Release Proposal and Development Roadmap

This proposal outlines a structured yearly cadence aimed at ensuring consistency and predictability in the development and promotion of XLIFF. Key steps include publishing updates every May, targeting summer and early fall conferences for outreach, and maintaining an open submission policy. The process will involve community engagement, feature development, and a transparent approval method, including regular voting on submissions. Emphasis will be placed on fostering collaboration among implementers and tool makers to enhance the XLIFF 2.0 functionality and promote new module proposals.

kovit
Télécharger la présentation

Yearly Cadence for XLIFF 2.x Release Proposal and Development Roadmap

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. XLIFF 2.x release cadence Kevin O’Donnell JUNE 2014

  2. Proposal • Yearly cadence for consistency & predictability: publish every May • Target summer/early fall conferences for promotion & socialization (eg. LocWorld, Unicode) • Foster cycle of XLIFF development & integration among implementers / tool makers • Open & transparent submission policy • Standard template for submissions • Submitters encouraged to own feature specification work • Statement of use commitment as prerequisite to approval • TC will vote to approve submissions for development • New XLIFF modules • Changes to existing XLIFF 2.0 functionality • Promotion of extension to module • Shortest path through OASIS: single public review • Features not ready / not approved will be postponed • Statement of use is required prior to final voting • Keep list of ideas/items for subsequent 2.x release

  3. JUN-SEP OCT-DEC JAN-MAY • Call for submissions • Feature development • Approve OASIS standard • Survey usage of XLIFF 2.0 • Solicit submissions for new modules/changes • Review feedback on existing feature set/implementation • Engage with partner standards committee • Review submissions [October] • Vote on submissions [October] • Feature specification review & approval [November] • Completion of statement of use [November] • Preparation of Committee Draft [December] • Approve Committee Draft [7 days] • Publish Public Review [30 days] • Reconcile comments, update specification [21 days] • Approve and submit candidate specification [7 days] • Public review of candidate specification [60 days] • Ballot for OASIS Specification approval [14 days]

More Related