30 likes | 187 Views
XLIFF 2.x release cadence. Kevin O’Donnell JUNE 2014. Overview. Yearly cadence for consistency & predictability: publish every May Target summer/early fall conferences for promotion & socialization ( eg . LocWorld , Unicode )
E N D
XLIFF 2.x release cadence Kevin O’Donnell JUNE 2014
Overview • 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 • Keep list of ideas/items for subsequent 2.x release
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] • Preparation of Committee Draft [December] • Approve Committee Draft [7 days] • Publish Public Review [30days] • 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]