Welcome to the jQuery UI design & planning wiki
This is a public wiki to plan, design, document, and discuss the future of jQuery UI plugins, and theming support. This is not the jQuery UI documentation. Please feel free to contribute your ideas.
Learn more: vision and goals, team, plugin priortization process, development phases, wiki language styleguide, how to submit your plugin for inclusion.
Status summary
The latest release candidate (1.6rc6) is out. When we finish testing and making any necessary fixes, it will be released as 1.7. See http://blog.jquery.com/2009/02/12/jquery-ui-17-is-the-new-16/
This 1.7 release includes major and minor fixes and updates to each 1.5 component, one new plugin, and two major updates:
jQuery UI 1.7 final will ship with jQuery 1.3.2 and require jQuery 1.3 at a minimum. The release also has the following requirements:
- all blockers and criticals fixed (7 blockers open, 19 criticals open)
- all new bug-tickets triaged (0 un-triaged, http://tinyurl.com/ui-triage)
- all plugin docs updated - at a mininum: options, defaults, events, ui parameter, methods - see website triage list and demo page wireframe sketch
- documentation needs to be updated for 1.7 (especially changes since 1.6rc2). Documentation should include one simple demo for each option.
- each plugin will have complete functional specifications/requirements written from which unit tests can be written.
- unit test coverage should be greater than 1.6rc6. Shooting for 40-60% with no individual plugin less than 40%.
- An Upgrade Guide detailing very simply for each plugins what will be required when moving from 1.5.3 to 1.7, without having to read through the changelog and decifer what was an API change and what was a bug fix.
The next major release (aka 1.next) and candidates for inclusion are highest priority plugins currently in the dev branch
as well as any dependant utilities:
Maintenance 1.7 releases (1.7.1, 1.7.2, etc.) will be developed in branches, not in the trunk. A week or two after the 1.7 release is finalized, the trunk will change to version 1.8pre. No plugin will be moved from the dev branch to the trunk until it meets the same level of readiness as demonstrated by 1.7 final, in terms of design, specs, development, testing, documentation, and demos. This is true of major refactorings (of existing components) as well. They should be done in a dev branch, leaving the previous version in the trunk until the refactor is complete.
Full list of plugins planned for jQuery UI
You can sort this table by clicking on the table header for each column. Each page uses this widget template.
Learn from other's UI mistakes: check out the UI hall of shame.
Comments (0)
You don't have permission to comment on this page.