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

Roadmap #288

Open
vboctor opened this issue Apr 10, 2015 · 2 comments
Open

Roadmap #288

vboctor opened this issue Apr 10, 2015 · 2 comments

Comments

@vboctor
Copy link
Contributor

vboctor commented Apr 10, 2015

Let's use this issue to brainstorm on the roadmap. The goal is to figure out the big rocks that we have to tackle and not necessarily the exact timeline.

2.0

  • Open sourcing
  • Build system
  • Publishing package
  • Lots of fixes
  • Package re-organization
  • Code style fixes
  • Dependency upgrades

2.x / 3.0

  • Support newer versions of Exchange / Exchange Online
  • Support OAuth
  • Close the gap with EWS Managed API
  • More fixes
@serious6
Copy link
Member

Maybe in addition to the things been said we should keep track on the following tickets:

2.0

2.x

3.0

  • extract autodiscover package and provide it as an independent project for reusability

independent tasks

@hariregula
Copy link

hariregula commented Mar 12, 2018

any progess on this invalid xml issue?I have lot of emails failing while reading for testing purpose. Help will be appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants