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

docs: update roadmap accordig to recent changes #397

Merged
merged 2 commits into from
Apr 8, 2022
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 10 additions & 13 deletions ROADMAP.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,7 @@

- Jira-GitHub, Jira-GitLab integration
- Jenkins-GitHub, Jenkins-GitLab integration
- HashiCorp Vault
- ArgoCD-GitHub SSO integration
- Repository bootstrapping for Python/Nodejs for GitHub
- Repository bootstrapping for Golang/Python/Nodejs for GitLab
Expand All @@ -15,33 +16,29 @@

## 2 Technical Roadmap

### Automated End-to-End Testing in a Staging Environment

- AWS EC2 (linux-amd64) creation with Terraform/Ansible
- Push notification to Slack/Lark when the testing environment is occupied or released

### Automated Release

- When a new tag is generated, build binaries for different platforms/OS and distribute the binaries to the plugin storage.

### Plugin Storage

Background: currently, we use GitHub releases to store pre-built binaries and plugins. We might need to figure out a better way to store/distribute plugins and binaries.

- Consider AWS S3 or similar choices for plugin storage.
- Make sure people who don't have optimum internet connections (e.g., users behind firewall or proxy) can still use DevStream smoothly.

### Plugins Dependency Management
### Automated End-to-End Testing in a Staging Environment

- Parallel/concurrency for plugins.
- AWS EC2 (linux-amd64) creation with Terraform/Ansible
- Push notification to Slack/Lark when the testing environment is occupied or released

### Misc

- Shorter CI time: for example, adding packages into a base image.
- Send push notification to core committers when there is a pull request ready for review.
- Shorter CI time: for example, adding packages into a base image
- More end-to-end tests coverage, to test more typical usecases and plugins
- Push notification to core committers when there is a new PR ready for review

## 3 Already Done

v0.3.1:
- automated release: when a new tag is generated, build binaries for different platforms/OS and distribute the binaries to the plugin storage.

v0.3.0:
- "Destroy" and "force delete": everything can be cleared up without any residue or side effects.
- "Output": all plugin's output is printed for users to review.
Expand Down