Add Build team vision and goals to Direction page
Merge request reports
Activity
@marin Can you take a look and let me know what you think?
mentioned in issue gitlab-org/omnibus-gitlab#2419 (closed)
@joshlambert Please put it in alphabetic sorted location. i.e. make it the first section under Direction before Chat Commands.
added 1 commit
- 0417d3c1 - Attempt to pull more than 100 direction issues.
added 398 commits
-
0417d3c1...b661ac55 - 397 commits from branch
master - c0209f31 - Merge branch 'master' into '1416-add-build-team-vision-and-goals-to-direction-page'
-
0417d3c1...b661ac55 - 397 commits from branch
added 1 commit
- 07fb73aa - Revert change to attempt more than 200 direction issues
assigned to @markpundsack
@markpundsack can you review?
The one outstanding issue unrelated to the Build items that we have exceeded 100 direction items for gitlab-ce. I spent some time trying to fetch the second page but couldn't get it to work. Don't want to have that slow this down so will open a separate issue to track, it is mostly affecting the Prometheus items I believe.
added 1 commit
- 01030d27 - Fix HA label now that we have moved items over.
I have updated the direction and vision goals for the build team to outline what we discussed yesterday as our primary deployment methods and features.
I tried to state what we were focused on delivering as benefits to users, and in broad strokes the methods we identified. I did not want to get too proscriptive, especially in regards to alternate methods as it didn't seem to be worth the risk to other potential partners / opportunities.
Note we will be fleshing out additional issues for HA and automation shortly. Keep in mind some are rolling into the 9.4 milestone so they don't appear under the broader Direction section.
Please let me know what you all think, thanks!
122 122 123 123 <%= wishlist["chat commands"] %> 124 124 125 ### Build and packaging 126 127 GitLab is the engine that powers many companies' software businesses so it is important to ensure it is as easy as possible to deploy, maintain, and stay up to date. 128 129 Today we have a mature and easy to use Omnibus based build system, which is the foundation for nearly all methods of deploying GitLab. It includes everything a customer needs to run GitLab all in a single package, and is great for installing on virtual machines or real hardware. We are committed to making our package easier to work with, highly available, as well as offering automated deployments on cloud providers like AWS. 130 131 We also want GitLab to be the best cloud native development tool, and offering a great cloud native deployment is a key part of that. We are focused on offering a flexible and scalable container based deployment on Kubernetes, by using enterprise grade Helm Charts. 132 133 #### GitLab High Availability 134 <%= wishlist["HA"] %> 135 136 #### Cloud Native Deployment 137 <%= wishlist["cloud images"] %> This includes https://gitlab.com/gitlab-org/omnibus-gitlab/issues/2391, which based on recent conversations seems to be more about providing an easy enterprise-level install rather than being cloud native. Is the tag perhaps not a direct mapping to the section?
@joshlambert LGTM. Merge it!
@joshlambert I'd recommend adding a catchall for anything labeled with Build and Direction, but not tagged with one of those three key areas.
Agree @markpundsack, we also need to create a new
cloud nativetag to resolve the above situation (AWS is a cloud image related issue, but not cloud native). Will get both of these done and then merge.Merging. Also added a new option to the wishlist generation to restrict generation to a specific project, this way we can specifically include just
directionissues from the Omnibus project.Edited by Joshua Lambertmentioned in commit 68cf4af0
