-
Notifications
You must be signed in to change notification settings - Fork 9
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
Create ROADMAP.md #943
base: develop
Are you sure you want to change the base?
Create ROADMAP.md #943
Conversation
Briefly describe future plans for MDS-Core
|
Work-in-progress. These are Lacuna priorities; feedback from other MDS-Core contributors is welcome. | ||
|
||
* Improved documentation for MDS-Core operation | ||
* Multi-MDS-version support (MDS 1.0 and later) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for sharing! After our meeting we discussed this internally and wondered, if you plan this two-way, or if you are only thinking about the agency api?
Here is an example: Would GET /policies with an Accept
header for Version 1.0
actually return the policy in 1.0
, even if the mds-core repo has already adapted MDS 1.2
(assuming there are any differences in a policy 1.0
vs. 1.2
)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe that's the case, yes.
* Passenger Services deployment for LADOT (MDS 2.0 alpha) | ||
* Add support for new modes architecture (MDS 2.0 final) | ||
* Increased test coverage | ||
* Support non-AWS cloud providers |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Azure and...what was the other one?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
GCP
* Add support for Policy Requirements (MDS 1.2) | ||
* Passenger Services deployment for LADOT (MDS 2.0 alpha) | ||
* Add support for new modes architecture (MDS 2.0 final) | ||
* Increased test coverage |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are there particular packages you have in mind as lacking in test coverage right now? I think most of the service packages in mds-core are all right. Is there a global maximum of line coverage we should be shooting for? I've been on a team once where we went for 95% which struck me as a tad excessive, but 80 feels pretty good.
Briefly describe future plans for MDS-Core