-
Notifications
You must be signed in to change notification settings - Fork 762
Work in progress
This page contains a candid and non-contractual list of what we are currently working on, either from a design or engineering standpoint. Some work might already be finished but awaiting proper documentation.
You can see our full board by visiting the ZenHub page that shows what is in the backlog, bullpen, in progress and in review. (This does require signing in to ZenHub with your GitHub account).
ZenHub Board: https://app.zenhub.com/workspace/o/vmware/clarity/boards?repos=69590701
| Item | Status | ETA |
|---|---|---|
| Website design improvements | In Progress | Spring 2020 (4.0) |
| Item | Status | ETA |
|---|---|---|
| Buttons for @clr/core | Complete | Fall 2019 (3.0) |
| Migrate icons to new @clr/core | Complete | Early 2020 (3.0) |
| Slider component | Complete | Early 2020 (3.0) |
| Datalist component | Complete | Early 2020 (3.0) |
| Angular 9 + Ivy Support | Complete | Early 2020 (3.0) |
| Alerts (@clr/core) | In Review | Spring 2020 |
| Reordering datagrid columns | In Review | Spring 2020 (4.0) |
| Combobox component | In Progress | Spring 2020 (4.0) |
| Modals for @clr/core | In Queue | Spring 2020 (4.0) |
| Design Tokens (@clr/core) | In Queue | Spring 2020 (4.0) |
| Generic Form Containers | In Queue | Spring 2020 (4.0) |
| Input Groups | In Queue | Spring 2020 (4.0) |
| Stepper Enhancements | In Queue | Spring 2020 (4.0) |
| Migrate @clr/core treeshakeable icons to @clr/angular | In Queue | Spring 2020 (4.0) |
| Forms (@clr/core) | In Queue | Fall 2020 |
| Remove inline font from CSS | Blocked | Unknown |
| Pin the first column in datagrid | Blocked | Unknown |
| Item | Status | ETA |
|---|---|---|
| Theming Documentation Improvements | Complete | 2020 (3.0) |
| Website improvements | In Progress | 2020 |
| Item | Type | Estimated Start |
|---|---|---|
| 3.0 Release | Development | Feb 2020 |
All ETAs are subject to change. We try our best to allow for changing priorities or discovery but estimation is an inexact science when it comes to software. When possible, we skew our estimates towards the liberal side of things. This is on purpose.
If your project requires a feature or component from our library to release, we are doing a disservice by being overly optimistic on our timelines. Which brings us to our next item:
If our ETA doesn't give you at least several weeks to integrate our changes into your app, go to Plan B. If our date slips because we were pulled onto another priority or because a new feature requires more refactoring than we had anticipated, you need to plan ahead as if that feature will not be ready in time. In general, our estimations are good. In general, we deliver on or before our estimates. But at the end of the day, delivering quality components takes as long as it will take. And even if we deliver some new feature under the wire and just in time, your project will need time to upgrade to the new release and validate against any breaking changes or deprecations.
That said, if you find yourself at issue with our priorities or want to see if you can lend a helping hand in the interest of moving something along, please email me at wilkenj@vmware.com. We are open source and welcome contributions from the community. Oftentimes, the difference between "getting what you want" and "getting what you want when you need it" is being a proactive member of the community.
Thanks for building with Clarity!