Skip to content
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

1.0 Release Plan #115

Open
nmetulev opened this issue Jul 18, 2019 · 0 comments

Comments

@nmetulev
Copy link
Collaborator

commented Jul 18, 2019

1.0 Release Plan

This plan captures our work for the 1.0 release. The goal is to have a strong release and focus on adding highly requested components, improving existing components by ensuring web framework and web standard compatibility, and avoiding any future breaking changes. To ensure a quality release, we are not committing to a date for this release. However, we expect the release to land before the end of the summer. Read on for more details on what we have planned for this release

We will continue to publish preview releases until 1.0 is released.

The plan

Below is a summary of the top level plan items. These items are in addition to everything that was initially released with the preview.

Legend of annotations:

Symbol Description
0️⃣ priority 0 - must have for this release
1️⃣ priority 1 - nice to have for this release
2️⃣ priority 2 - stretch goal - unlikely for this release but we will try our best
❗️ missing issue reference
🔦 investigating

New components

  • 0️⃣ PeoplePicker input component - #105
  • 0️⃣ PersonCard component - #106
  • 2️⃣ ❗️ Calendar component - evolution of the agenda component with day/week/month view

Component improvements:

  • 0️⃣ All components should be accessible - #2
  • 0️⃣ All components should enable developers to localize them - #102
  • 1️⃣ ❗️ Update mgt-tasks and mgt-agenda to use mgt-people instead of multiple instances of mgt-person
  • 1️⃣ Add ability to template component with 3rd party template libraries - #89
  • 1️⃣ Add built in theme support - #97
  • 2️⃣ ❗️ 🔦 Enable full styling by adding an option to disable the shadow root

Providers:

  • 0️⃣ Teams provider incremental consent support - #92
  • 1️⃣ ❗️ New on behalf of provider that supports authentication and graph access through a back end service
  • 2️⃣ Office add-in provider - #13

Graph access

  • 1️⃣ Add support for batching calls - #30
  • 1️⃣ ❗️ 🔦 Add support for caching of calls

Developer experience

  • 0️⃣ ❗️ Add more samples to documentation and examples of using APIs both through the CDN and NPM
  • 0️⃣ ❗️ Remove docs from this repo and only use the docs repo (https://github.com/microsoftgraph/microsoft-graph-docs) (#124)
  • 1️⃣ ❗️ 🔦 Add inline demos to documentation
  • 1️⃣ ❗️ 🔦 Enable developers to extend our base classes to easily create custom components
  • 2️⃣ 🔦 Create a demo page on github pages to showcase components and create samples - #4
  • 2️⃣ ❗️ 🔦 Build bundles without msal dependency to enable developers to use a different version of msal

Engineering

  • 0️⃣ ❗️ Ensure all code is documented through tsdocs
  • 0️⃣ ❗️ 🔦 Investigate improvements to our unit testing
  • 1️⃣ 🔦 Add end to end testing - #42

@nmetulev nmetulev self-assigned this Jul 18, 2019

@nmetulev nmetulev pinned this issue Jul 18, 2019

@nmetulev nmetulev changed the title 1.0 Release Plan [Draft] 1.0 Release Plan Jul 19, 2019

@msftbot msftbot bot added In-PR :shipit: and removed In-PR :shipit: labels Aug 19, 2019

@vogtn vogtn referenced this issue Aug 20, 2019
0 of 5 tasks complete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.