-
Notifications
You must be signed in to change notification settings - Fork 134
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
3 changed files
with
166 additions
and
75 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,86 @@ | ||
| # Technology Refresh | ||
|
|
||
| The focus for the first part of 2018 is to complete the move from AngularJS to Angular. This is a significant amount of work. | ||
|
|
||
| ## Migrate Angular from AngularJS | ||
|
|
||
| Move to a newer framework that is being actively developed and will carry us forward for longer. This will make future migrations much easier (Angular 2 => 4 => 5 => 6) | ||
|
|
||
| Note: | ||
| - Back-end stays the same (folder structure will most likely be moved around) | ||
| - Deployment and other scripts, artefacts remain the same (tweaks as necessary to build the V2 code) | ||
|
|
||
| Stack: | ||
|
|
||
| - Angular 5 | ||
| - Typescript | ||
| - RxJS | ||
| - Angular Material | ||
|
|
||
| ## Migrate to Material Design | ||
|
|
||
| Adopt material design while keeping essence of the current Angular 1 app: | ||
|
|
||
| - Use Material Design as the visual language for the UX | ||
| - Rich language | ||
| - Used by a growing number of projects, not just those from Google | ||
| - Adopt Material Design approach, patterns and components | ||
| - Leverage angular-material library for UI components | ||
| - Only create custom components when needed | ||
| - Adopt angular-material approach to theming | ||
| - Improve layout and use more visual cues to help locate date and issues | ||
|
|
||
|
|
||
| # Migration Milestones | ||
|
|
||
| > This material is out of date. We will update once schedule planning is complete. | ||
| ### Milestone 1: CF Applications -> Endpoint mgmt and Application views (Complete in Sprint 22) | ||
|
|
||
| - App Wall | ||
| - App View | ||
| - Edit | ||
| - Routes | ||
| - Instances | ||
| - SSH | ||
| - Endpoints | ||
|
|
||
| ### Milestone 1b (Complete in Sprint 22) | ||
|
|
||
| - Deployment of an Application as per V1. | ||
|
|
||
| ### Milestone 2 (Complete in Sprint 24) | ||
|
|
||
| - Cloud Foundry View (excluding "assign users") | ||
|
|
||
| ### Milestone 3 (Complete in Sprint 26) | ||
|
|
||
| - Services view | ||
| - Services as a top-level concept | ||
| - Improve support for services: Service Keys etc | ||
|
|
||
| ### Milestone 4: Misc (Complete in Sprint 28) | ||
|
|
||
| - Add dashboard | ||
| - About page | ||
| - User profile viewing and edit | ||
|
|
||
| ### Milestone 5 (Complete in Sprint 30) | ||
|
|
||
| - Equivalent functionality of "Assign Users" | ||
|
|
||
| ### To be scheduled into Milestones: | ||
|
|
||
| - e2e tests | ||
| - unit tests | ||
| - error handling | ||
| - Support for plugins/extensions | ||
| - Support for vendor modifications | ||
| - Internationalisation (i18n) | ||
| - Theming/Branding | ||
| - Deployment support | ||
| - cf push | ||
| - docker compose | ||
| - helm | ||
| - bosh | ||
|
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,86 +1,32 @@ | ||
| # Stratos Roadmap | ||
|
|
||
| Last Updated: 31 January 2018 | ||
|
|
||
| The current high-level features are: | ||
|
|
||
| * Angular 2 - move to Angular 2 for the front-end UI | ||
| * Services - make Services a first-class citizen in the UI - See [here](planning/services.md) | ||
| * Metrics - add metrics to Stratos. See [here](planning/metrics.md) for some initial thoughts | ||
|
|
||
| Last Updated: 25 April 2018 | ||
|
|
||
| ## Agile | ||
|
|
||
| We work on a 2-week Sprint cycle. Sprints start on Wednesdays. For reference, Sprint 22 started 24 Jan 2018. | ||
|
|
||
| We are using GitHub issues to track all work items. We use ZenHub to manage these in an agile fashion - see: | ||
|
|
||
| https://app.zenhub.com/workspace/o/cloudfoundry-incubator/stratos/boards | ||
|
|
||
| ## Angular 2 | ||
|
|
||
| The focus for the first part of 2018 is to complete the move from AngularJS to Angular. This is a significant amount of work. | ||
|
|
||
| Note: | ||
| - Back-end stays the same (folder structure will most likely be moved around) | ||
| - Deployment and other scrpts, artefacts remaint the sames (tweaks as neccessary to build the V2 code) | ||
|
|
||
| Stack: | ||
|
|
||
| - Angular 5 | ||
| - Typescript | ||
| - RxJS | ||
| - Angular Material | ||
| - Material Design => Adopt material design while keeping essence of the current Angular 1 app | ||
|
|
||
| We plan to accomplish this work in a number of milestones, so that we reach parity with the AngularJS version. | ||
|
|
||
| ### Milestone 1: CF Applications -> Endpoint mgmt and Application views (Complete in Sprint 22) | ||
|
|
||
| - App Wall | ||
| - App View | ||
| - Edit | ||
| - Routes | ||
| - Instances | ||
| - SSH | ||
| - Endpoints | ||
|
|
||
| ### Milestonte 1b (Complete in Sprint 22) | ||
|
|
||
| - Deployment of an Application as per V1. | ||
|
|
||
| ### Milestone 2 (Complete in Sprint 24) | ||
| We work on a 2-week Sprint cycle. Sprints start on Wednesdays. For reference, Sprint 27 started 4 April 2018. | ||
|
|
||
| - Cloud Foundry View (excluding "assign users") | ||
| We are using GitHub issues to track all work items. We use ZenHub to manage these in an agile fashion - see: https://app.zenhub.com/workspace/o/cloudfoundry-incubator/stratos/boards | ||
|
|
||
| ### Milestone 3 (Complete in Sprint 26) | ||
| ## High-Level Features | ||
|
|
||
| - Services view | ||
| - Services as a top-level concept | ||
| - Improve support for services: Service Keys etc | ||
| The high-level features that we schedule into the roadmap are identified by the ```feature-request``` label. You can see the current set of features [here](https://github.com/cloudfoundry-incubator/stratos/issues?q=is%3Aopen+is%3Aissue+label%3Afeature-request). | ||
|
|
||
| ### Milestone 4: Misc (Complete in Sprint 28) | ||
| ### Near-term roadmap | ||
|
|
||
| - Add dashboard | ||
| - About page | ||
| - User profile viewing and edit | ||
| |#|Description|Issue|Notes| | ||
| |---|---|---|---| | ||
| |1|Technology Refresh (AngularJS => Angular)|[\#1972](https://github.com/cloudfoundry-incubator/stratos/issues/1972)|[Notes](planning/angular.md)| | ||
| |2|1st class support for service plan & service instance|[\#1391](https://github.com/cloudfoundry-incubator/stratos/issues/1391)|[Notes](planning/services.md)| | ||
| |3|Add support for Application and CF Metrics|[\#1985](https://github.com/cloudfoundry-incubator/stratos/issues/1985)|[Notes](planning/metrics.md)| | ||
| |4|Support UAA login UX directly|[\#1384](https://github.com/cloudfoundry-incubator/stratos/issues/1384)|| | ||
| |5|Deploy application: Enable deploying from private Git repositories|[\#1442](https://github.com/cloudfoundry-incubator/stratos/issues/1442)|| | ||
|
|
||
| ### Milestone 5 (Complete in Sprint 30) | ||
|
|
||
| - Equivalent functionality of "Assign Users" | ||
| ## Schedule | ||
|
|
||
| ### To be scheduled into Milestones: | ||
| We are currently focused on completing out the core features to get V2 on par with V1. | ||
|
|
||
| - e2e tests | ||
| - unit tests | ||
| - error handling | ||
| - Support for plugins/extensions | ||
| - Support for vendor modifications | ||
| - Internationalisation (i18n) | ||
| - Theming/Branding | ||
| - Deployment support | ||
| - cf push | ||
| - docker compose | ||
| - helm | ||
| - bosh | ||
| We will shortly review progress and the remaining work and publish a tentative schedule. | ||
|
|
||
| Beyond the release of V2, we expect to move to a sprit-based release schedule, publishing a new release every 2 weeks. |