Skip to content

chore: update readme status for November #1683

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 2, 2016
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 11 additions & 10 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,14 +28,15 @@ and which pieces are blocked) and make a comment.
Also see our [`Good for community contribution`](https://github.com/angular/material2/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+for+community+contribution%22)
label.

High level items planned for October 2016:
High level items planned for November 2016:
* Initial version of md-select
* Basic docs for dialog and snackbar
* Major bug bashing
* Start design on autocomplete and chips
* Continued bug bashing
* Initial versions of autocomplete and chips
* AoT compile e2e app
* Start work on https://material.angular.io site
* Onboarding for 3 (!) new Angular Material team members.
* Continue work on https://material.angular.io site
* Major refactoring for md-input
* Tabs animations
* Expanding e2e test coverage


#### Feature status:
Expand Down Expand Up @@ -64,14 +65,14 @@ High level items planned for October 2016:
| dialog | Started, not yet ready for release | [README][22] | [#114][0114] |
| snackbar / toast | Initial version, needs enhancements | [README][21] | [#115][0115] |
| select | Design started | - | [#118][0118] |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to put select as started? Given that the first PR is in master.

| textarea | Not started | - | [#546][0546] |
| autocomplete | Not started | - | [#117][0117] |
| chips | Not started | - | [#120][0120] |
| textarea | Started | - | [#546][0546] |
| autocomplete | Design started | - | [#117][0117] |
| chips | Design started | - | [#120][0120] |
| theming | Initial version, needs enhancements | [Guide][20] | - |
| prod build | Not started | - | - |
| docs site | UX design and tooling in progress | - | - |
| typography | Not started | - | [#205][0205] |
| layout | Not started | - | - |
| layout | Design in-progress, prototyped | - | - |
| fab speed-dial | Not started | - | [#860][0860] |
| fab toolbar | Not started | - | - |
| bottom-sheet | Not started | - | - |
Expand Down