Update for the Roadmap

.vs/VSWorkspaceState.json

@@ -2,6 +2,6 @@
   "ExpandedNodes": [
     ""
   ],
-  "SelectedNode": "\\Home.md",
+  "SelectedNode": "\\02.-Setting-eShopOnContainer-solution-up-in-a-Visual-Studio-2017-environment.md",
   "PreviewInSolutionExplorer": false
 }

01.-Roadmap-and-Milestones-for-future-releases.md

@@ -1,12 +1,16 @@
-## Version 0.1 (Current version - Early March 2017)
+## Version 0.1 (ALPHA, current version - Early March 2017)
+- Available at the MASTER branch.
 - Docker containers with .NET Core and Linux images support/tested
 - .NET 1.1 and EF 1.1 support 
-- (vs2017 branch) Plus, migrated to .csproj and Visual Studio 2017, including VS Docker Tooling requirements at the docker-compose.yml files
+- Visual Studio 2017 and .csproj support, including VS Docker Tooling based on docker-compose.yml files supporting multi-container debugging, etc. - CLI and VS Code environments are also supported.
+- Initial basic foundational microservice oriented architecture, easy to get started, described in this <a href='docs/architecting-and-developing-containerized-and-microservice-based-net-applications-ebook-early-draft.pdf'>**Guide/eBook** (Early DRAFT, still work in progress)</a>. 
 
-## Version 0.2 Roadmap (By mid-April 2017 timeframe)
+## Version 0.2 Roadmap (BETA, by mid-April 2017 timeframe)
 
 - Implement support for Windows Containers running on Windows NanoServer using different Docker base images instead of the Linux based images (.NET Core code should be the same as it is cross-platform) - Fork or the same repo?
 
+- Build/compile process within an Integration Container (with a provided Docker Image with all SDK dependencies) instead of in local PC. This would greatly simplify the CLI developer's installation requirements in a local machine. That integration container should also be used from a CI pipeline.
+
 - INTEGRATION EVENTS with Event-Bus implementations: Implement Event-Driven communication between microservices/containers based on Event-Bus interfaces and two implementation:
   1. (PRIORITY) Standalone Pub/Subs messaging implementation based on an out-of-proc RabbitMQ Container
   2. (Future version) Azure-attached implementation based on Azure Service Bus using Topics for Pub/Subs
@@ -60,7 +64,7 @@ We should probably implement Domain Events when implementing the SAGA example pl
 Our task here will be to use that new lib.
 
 - Topics to Review and document:
-   - API versioning Management for microservices. Techniques and things to have into account Related to Caos-Monkey, etc.
+   - API versioning Management for microservices. Techniques and things to have into account Related to Chaos Monkey, etc.
    - Solid API contracts (based probably on Swagger, but interoperable with any language and explicit per paramater)
 
 ## Future versions - Roadmap (After April 2017)
@@ -94,8 +98,6 @@ Actor model, stateful services, etc.
 
 - (To be Confirmed) In the Windows Containers fork, implement and add a simple WCF microservice/container implementing any logic like a simulated legacy Payment Gateway, as an example of "lift and shift" scenario.
 
-- (To be Confirmed) Build/compile process within an Integration Container (with a provided Docker Image with all SDK dependencies) instead of in local PC. This would greatly simplify the developer's installation requirements in a local machine. That integration container could also be used from a CI pipeline.
-
 - (To be Confirmed) Semantic log - Semantic logic - Related to the Azure app version and Application Insight usage
 Monitor what microservices are up/down, etc. related to App Insights, but the events are custom
 ETW events and "Semantic Application Log" from P&P