1.6 without plugins soon or 1.6 with plugins late?

1.6 without plugins soon or 1.6 with plugins late?

Hey everyone,
as most of you know, the 1.6 release should already be out for many weeks. Unfortunately, there were a couple of
things that held of the release: Ugly regressions, new team structures and to-be-refactored code.
The biggest issue, however, is that there's still almost nobody working on the test, so we have a very incomplete
imagine wether something actually works or not, and if it uses the API properly. So after digging through it manually,
we found out that the following modules cannot be released without a rewrite:
- Autocomplete (not UI conformant, only wrapped by the UI API)
- Colorpicker (doesn't use the internal components, fails in IE)
The following components are fairly safe and just need a bit more thought on it (from the Interaction Design Team):
- Spinner
- Progressbar
This means that while I'm not really happy about it, there are two options right now, since one of our core values
is not to release anything broken:
1) Release 1.6 soon (as in days), without autocomplete/colorpicker at least (still need to think about the other two)
2) Release 1.6 in 2-3 months, when current components I'm working on (menu/tooltips/grid/positionTo/selectables) are finished
    and we found the time to rewrite the other stuff.
Richard, Scott, Cody and me all voted for the first obviously, although it hurts to remove components that were
already announced in the blogs and in a rc release. We would like to hear more opinions on that.
Thanks a lot,
Paul<br clear="all">
--
Paul Bakaus
UI Architect
--
<a href="http://paulbakaus.com">http://paulbakaus.com</a>
<a href="http://www.linkedin.com/in/paulbakaus">http://www.linkedin.com/in/paulbakaus</a>