|
|
@@ -1,7 +1,7 @@
|
|
|
# Docker Roadmap
|
|
|
|
|
|
Thank you for the interest in Docker and our products!
|
|
|
-This is the public roadmap for Docker Products and Services (Hub, Desktop, Engine, docker-compose, Docker App,...).
|
|
|
+This is the public roadmap for Docker Products and Services (Hub, Desktop, Engine, docker-compose, Docker App).
|
|
|
|
|
|
# Introduction
|
|
|
We want to share with our customers what we plan to do early and often so we can get your feedback on if these are the right things for us to be focusing on. This also allows our customers to make early decisions based on what we are/are not building.
|
|
|
@@ -46,9 +46,10 @@ If you think you’ve found a potential security issue, please do not post it in
|
|
|
* [Docker Desktop Mac](https://github.com/docker/for-mac/issues)
|
|
|
|
|
|
**Q:** What do the roadmap categories mean?
|
|
|
-* Shipped - Hopefully you are enjoying it!
|
|
|
-* Working on it - Actively in development, we are trying to get this out to you in a good state as soon as we can.
|
|
|
-* We're Writing the Code - The next thing we are thinking about working on or addressing as part of our public roadmap
|
|
|
+* Shipped - Hopefully you are enjoying it! Give us feedback on how it is working!
|
|
|
+* Developer Preview/Edge - For Docker Desktop Only - In developer preview on the Docker Desktop Edge Channel. See links above for where to find it!
|
|
|
+* Almost There - We are applying the finishing touches. Things in this bucket you can expect to be shipped within 2-4 weeks.
|
|
|
+* We're Writing the Code - Actively in development, we are trying to get this out to you in a good state as soon as we can.
|
|
|
* Investigating - We're thinking about it. This might mean we're still designing, or thinking through how this might work. This is a great phase to send how you want to see something implemented! We'd love to see your usecase or design ideas here.
|
|
|
|
|
|
**Q:** Why are there no dates on your roadmap?
|
|
|
@@ -56,15 +57,16 @@ If you think you’ve found a potential security issue, please do not post it in
|
|
|
**A:** Because we know things change and we want the room to do the right thing by fixing security issues as they come up or helping people out where they need. This means we might have to change our priorities and don’t want to let people down.
|
|
|
|
|
|
**Q:** How can I provide feedback or ask for more information?
|
|
|
-**A:** Please open an issue!
|
|
|
+
|
|
|
+**A:** Please open an issue in this repo! If the issue is a bug or security issue, please follow the separate instructions above.
|
|
|
|
|
|
**Q:** How can I request a feature be added to the roadmap?
|
|
|
|
|
|
-**A:** Please open an issue! You can read about how to contribute here. Community submitted issues will be tagged "Proposed" and will be reviewed by the team.
|
|
|
+**A:** Please open an issue! You can read about how to contribute [here](https://github.com/docker/roadmap/blob/master/CONTRIBUTING.MD). Community submitted issues will be tagged "Proposed" and will be reviewed by the team.
|
|
|
|
|
|
**Q:** Will you accept a pull request?
|
|
|
|
|
|
-**A:** We haven't worked out how pull requests should work for a public roadmap page, but we will take all PRs very seriously and review for inclusion. Read about contributing.
|
|
|
+**A:** We haven't worked out how pull requests should work for a public roadmap page, but we will take all PRs very seriously and review for inclusion. Read about contributing. We review these each week.
|
|
|
|
|
|
# License
|
|
|
This library is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License.
|
Justin Graham