ZedAI 2010 Release Schedule
From zedwiki
Contents |
Constraints
It is anticipated that we will have a Draft Specification for Test Use (DSFTU) ready by mid-January. That leaves three months from the projected next release, which translates into 2.5 months factoring out holiday absences around the end of year.
Based on our next release going out by Friday, Oct. 15, we could squeeze two more smaller and more focussed releases in before the holiday break, leaving 2-3 weeks in the new year to identify any issues arising out of these releases (i.e., we wouldn't address any new updates after the second release unless they are determined to be critical).
Possible Release Breakdown
Oct. 15 - Major Release for annotation/object/note/by/description/etc.
Nov. 19 - Four weeks to address major issues (final week for wrap-up call / release).
Dec. 17 - Three weeks to address new issues (final week for wrap-up call / release).
Jan. 21 - Early January to wrap up and release DSFTU.
Priorities
In order to get a DSFTU, we need to focus on finalizing the specification and associated technologies first (i.e., we don't want to fundamentally change the nature of the specification during or after).
All markup/validation issues should be dropped to secondary status, as a result, as their finalization is not required as part of the spec. release process, and they can continue to be addressed through the review period and beyond as new needs are identified.
In terms of addressing the markup issues, missing required functionality in the current element set should be priority.
Nov. 12
This release should finalize our stance on all external technologies. In order of priority:
- use/implementation of RDFa 1.1 (primary unknown quantity still remaining)
- the level of CSS support expected and implications of non-css equivalents - issue 162
- XML version - issue 108
- CSS association revision - issue 106
Open issues in the specification prose should be the next priority, namely:
- reviewing the processing agent requirements
- updating public components prose in specification - issue 130
And as time permits, address implementation issues:
- identification of schema type in RD
- documentation/formalization of Content Selection feature
Dec. 17
Ensure all validation requirements are in place for current profiles:
Markup requirements as time permits:
- adding publisher address - issue 142
- extensibility of abbreviation types - issue 148
- linebreaks - issue 164
- separator/cbr - issue 163
Jan. 21
Verify all snippets and longdescs are still accurate.
