Commit c9819143 authored by Hanif Smith-Watson's avatar Hanif Smith-Watson
Browse files

Update broken internal links

parent d7604cdc
......@@ -159,7 +159,7 @@
- title: Kanban Boards
description: Visually prioritize, manage, and track work execution with powerful and flexible kanban boards.
text: Kanban Boards
url: https://about.gitlab.com/product/kanban-boards/
url: https://about.gitlab.com/stages-devops-lifecycle/issueboard/
columns:
- icon_url: /images/devops-tools/gitlab-logo.svg
icon_grayed: false
......
......@@ -10,5 +10,5 @@ features:
categories:
- "Cloud Native Installation"
description: |
- The culmination of work spread across several releases results in greater than 5x reduction in time to initialize Rails based pods, and a 25% reduction in application process startup. This results in significantly faster scaling of the Webservice and Sidekiq deployments. For more details on the implemented solutions, see multiple associated issues: [gitlab-org/charts/gitlab#1775](https://gitlab.com/gitlab-org/charts/gitlab/-/issues/1775), [gitlab-org/charts/gitlab#1361](https://gitlab.com/gitlab-org/charts/gitlab/-/issues/1361), [gitlab-org/charts/gitlab#1779](https://gitlab.com/gitlab-org/charts/gitlab/-/issues/1779), [gitlab-org/build/CNG!433](gitlab-org/build/CNG!433), [gitlab-org/charts/gitlab#2165](https://gitlab.com/gitlab-org/charts/gitlab/-/issues/2165).
- The culmination of work spread across several releases results in greater than 5x reduction in time to initialize Rails based pods, and a 25% reduction in application process startup. This results in significantly faster scaling of the Webservice and Sidekiq deployments. For more details on the implemented solutions, see multiple associated issues: [gitlab-org/charts/gitlab#1775](https://gitlab.com/gitlab-org/charts/gitlab/-/issues/1775), [gitlab-org/charts/gitlab#1361](https://gitlab.com/gitlab-org/charts/gitlab/-/issues/1361), [gitlab-org/charts/gitlab#1779](https://gitlab.com/gitlab-org/charts/gitlab/-/issues/1779), [gitlab-org/build/CNG!433](https://gitlab.com/gitlab-org/build/CNG/-/merge_requests/433), [gitlab-org/charts/gitlab#2165](https://gitlab.com/gitlab-org/charts/gitlab/-/issues/2165).
- Kubernetes 1.13 is now the minimum supported version. Support for Kubernetes 1.12 was dropped in this release. For more details, see [the removal notice](#kubernetes-1.12-no-longer-supported).
......@@ -512,7 +512,7 @@ features:
- GitLab 11.1 ships with [Mattermost 5.0](https://mattermost.com/blog/mattermost-5-0-intercept-and-modify-posts-advanced-permissions-longer-posts-and-more/),
an [open source Slack-alternative](https://mattermost.com) whose newest release includes a post
interception feature, increased character limit on posts, combined join/leave messages, plus much more.
- Raspberry Pi packages are now available for [Raspbian Stretch](../../../../installation/#raspberry-pi-2).
- Raspberry Pi packages are now available for Raspbian Stretch.
- Omnibus has been updated to 5.6.12.
- Prometheus can now be configured to [read and write to remote services](https://docs.gitlab.com/omnibus/settings/prometheus.html#remote-read-write).
- Prometheus exporters have been updated, and some metric names have changed: node_exporter 0.16.0, alertmanager 0.15.0, postgres_exporter 0.4.6, redis_exporter 0.20.2.
......
......@@ -43,7 +43,7 @@ At GitLab, we believe in a world where everyone can contribute, and we're buildi
- **Collaborate** with team members, internal and external stakeholders, and executive sponsors, using the same set of single-source-of-truth artifacts in a single application.
- **Measure** the efficacy of the entire process, characterizing the flows with value streams, thus providing actionable insight for continuous improvement.
Regardless of your agile methodology ([Kanban](https://about.gitlab.com/product/kanban-boards/), [Scrum](https://about.gitlab.com/solutions/agile-delivery/), or [SAFe](https://about.gitlab.com/solutions/agile-delivery/scaled-agile/)), GitLab's flexible and powerful approach to agile planning can support your needs. Join us and contribute to our [Agile Planning vision](https://about.gitlab.com/direction/plan/).
Regardless of your agile methodology ([Kanban](https://about.gitlab.com/stages-devops-lifecycle/issueboard/), [Scrum](https://about.gitlab.com/solutions/agile-delivery/), or [SAFe](https://about.gitlab.com/solutions/agile-delivery/scaled-agile/)), GitLab's flexible and powerful approach to agile planning can support your needs. Join us and contribute to our [Agile Planning vision](https://about.gitlab.com/direction/plan/).
Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner research publications consist of the opinions of Gartner’s research organization and should not be construed as statements of fact. Gartner disclaims all warranties, express or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose.
......
......@@ -67,7 +67,7 @@ To make the project template available when creating a new project, the vendorin
```bash
bin/rake gitlab:update_project_templates[$name]
```
1. Run the [bundle_repo](/bundle_repo) script. Make sure to pass the correct arguments, or the script may damage the folder structure.
1. Run the `bundle_repo` script. Make sure to pass the correct arguments, or the script may damage the folder structure.
1. Add exported project (`$name.tar.gz`) to `gitlab/vendor/project_templates` and remove the resulting build folders `tar-base` and `project`
1. Run `bin/rake gettext:regenerate` in the `gitlab` project and commit new `.pot` file
1. Add changelog (e.g. `bin/changelog -m 25486 "Add Project template for .NET"`)
......
......@@ -18,7 +18,7 @@ We are passionate about [all remote working](/company/culture/all-remote/vision/
Those activities and behaviors include:
* [DIB Events](/company/culture/inclusion/diversity-and-inclusion-events/)
* [DIB Advisory Group](/company/culture/inclusion/global-diversity-inclusion--belonging-advisory-group)
* [DIB Advisory Group](/company/culture/inclusion/#global-diversity-inclusion--belonging-advisory-group)
* [Diversity, Inclusion & Belonging TMRGs - Team Member Resource Groups](/company/culture/inclusion/#ergs---employee-resource-groups)
* [Our Values](/handbook/values/)
* [Family and Friends first, Work second](/handbook/values/#family-and-friends-first-work-second)
......
......@@ -23,7 +23,7 @@ canonical_path: "/company/team/structure/working-groups/sharding/"
## Outcome - Closed
We have decided to close this Sharding focused working group and will open a [Scaling Working Group](/company/team/structure/working-groups/scaling/) with a different focus. The initial focus of this Sharding working group was to increase the scalability of our database with a long-term goal of 100x scalability. At the onset of this group, it was theorized that we would hit a database scalability wall within 6-12 months. Subsequent analysis and incremental scalbility efforts have indicated that we have significantly more scaling headroom. Based on the analysis we have a high degree of confidence that the current architecture is in good shape to handle our needs for the next 12 months: [Database Capacity and Saturation Analysis (Iteration 1)](https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/10340) This analysis will continue on a monthly basis. We have also identified areas of incremental database scalability that has been prioritzed by the database team: [Reduce total size and growth of GitLab.com's PostgreSQL database](https://gitlab.com/groups/gitlab-com/-/epics/374). Between the ongoing analysis and incremental database improvements we have greatly reduced the urgency of database scalability.
We have decided to close this Sharding focused working group and will open a Scaling Working Group with a different focus. The initial focus of this Sharding working group was to increase the scalability of our database with a long-term goal of 100x scalability. At the onset of this group, it was theorized that we would hit a database scalability wall within 6-12 months. Subsequent analysis and incremental scalbility efforts have indicated that we have significantly more scaling headroom. Based on the analysis we have a high degree of confidence that the current architecture is in good shape to handle our needs for the next 12 months: [Database Capacity and Saturation Analysis (Iteration 1)](https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/10340) This analysis will continue on a monthly basis. We have also identified areas of incremental database scalability that has been prioritzed by the database team: [Reduce total size and growth of GitLab.com's PostgreSQL database](https://gitlab.com/groups/gitlab-com/-/epics/374). Between the ongoing analysis and incremental database improvements we have greatly reduced the urgency of database scalability.
Additionally, we have come to the consensus that sharding is not the desired approach for our long term scalability needs. This decision was informed through investigation, proofs of concept, research, interviews and various implementation proposals. Here's a brief list of items that helped to inform our decision to close this working group:
......
......@@ -25,4 +25,4 @@ GitLab Enterprise Edition 6.3.1 is available for subscribers at [GitLab Cloud](h
Update instructions can be [found](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/update/patch_versions.md) [here](https://about.gitlab.com/update/).
### Workarounds
Users who cannot upgrade can address the DoS vulnerability by applying [this patch based on the workaround provided by Rails](/files/0001-Monkey-patch-for-CVE-2013-6414.patch) in `/home/git/gitlab` with `git am` and restarting GitLab.
Users who cannot upgrade can address the DoS vulnerability by applying a patch based on the workaround provided by Rails in `/home/git/gitlab` with `git am` and restarting GitLab.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment