data/release_posts/2017_12_22_gitlab_10_3_released.yml

@@ -4,7 +4,7 @@ features:
     - name: Static Application Security Testing (SAST)
       available_in: [eeu]
       documentation_link: 'https://docs.gitlab.com/ee/user/project/merge_requests/sast.html'
-      documentation_text: "Read through the documentation on SAST in Auto DevOps"
+      documentation_text: "Read through the documentation on SAST"
       image_url: '/images/10_3/sast.png'
       reporter: bikebilly
       issue_url: 'https://gitlab.com/gitlab-org/gitlab-ee/issues/3723'
@@ -47,15 +47,9 @@ features:
         performance impact of a merge request for web apps. Browser Performance
         Testing runs a headless browser to simulate visiting one or more pages
         of your application and analyzes them. A summary of performance changes
-        is provided on the merge request so you're aware of performance impact
+        is provided on the merge request so you're aware of the performance impact
         *before* merging into `master`.
-        Browser Performance Testing is also now [included in Auto
-        DevOps](https://docs.gitlab.com/ee/topics/autodevops/#auto-browser-performance-testing),
-        and we have [great
-        improvements](https://gitlab.com/gitlab-org/gitlab-ee/issues/4371)
-        coming.
-
     - name: Merge Request Commit Discussions
       available_in: [ce, ees, eep]
       documentation_link: 'https://docs.gitlab.com/ee/user/discussions/#commit-discussions-in-the-context-of-a-merge-request'
@@ -119,13 +113,18 @@ features:
       reporter: bikebilly
       issue_url: 'https://gitlab.com/gitlab-org/gitlab-ee/issues/3734'
       description: |
+        **Note:** During 10.3 release testing, we found a critical problem with this feature.
+        We recommend to avoid adding more than one cluster for now, and in case you already have,
+        remove it immediately. A fix has already been developed and is ready to be shipped
+        with GitLab 10.3.1, probably early next week.’
+
         GitLab can easily deploy your application to different environments
         within a Kubernetes cluster. We commonly see Development, Staging, and
-        Production, and Review Apps all published in the same way. But up until
-        now, they all needed to live in the same cluster. This is suboptimal for
-        keeping data separated and secure. Everything in a single cluster may
-        not even be an option for you if regulations require you to deploy to
-        physically different locations to stay compliant.
+        Production, and Review Apps all published in the same way.
+        Up until now, they all lived in the same cluster and you may have the
+        need to keep data separated, for example if regulations require
+        you to store production data to a physically different location, or
+        you want to enforce strict data isolation in your infrastructure.
         With GitLab 10.3, you can configure multiple clusters for each project,
         each linked to a specific environment, so the right cluster is
@@ -141,15 +140,13 @@ features:
       reporter: bikebilly
       issue_url: 'https://gitlab.com/gitlab-org/gitlab-ce/issues/38962'
       description: |
-        In GitLab 10.0 we released Auto DevOps (still in Beta) and users can
-        enable it for their projects. However the first pipeline, and thus the
-        first deployment to production, doesn't happen until the first push
-        after saving.
-        With GitLab 10.3, when enabling Auto DevOps for your project, a pipeline
-        is automatically run on your default branch, and you can immediately
-        jump to the pipelines page to follow what's going on. This is a much
-        more natural flow and easier introduction to the power of Auto DevOps.
+        Previously in GitLab if you enabled Auto DevOps you still had to wait until
+        you pushed a commit before your pipelines would populate.
+        This was a confusing experience that didn't follow expected behavior.
+        With GitLab 10.3, a pipeline for your project will be run as soon as you
+        enable Auto DevOps in Settings, so you can immediately see results without
+        needing to push another commit to your code.
     - name: Strict check on artifacts dependencies
       available_in: [ce, ees, eep]
@@ -167,11 +164,10 @@ features:
         inconsistent states where code is expecting to find resources that are
         not available, creating errors that are hard to spot and debug.
-        In GitLab 10.3, we introduce strict checking on these dependencies, and
-        jobs will fail if their dependencies cannot be found. Because of this,
-        now you'll always be aware if something required is missing, and you can
-        take proper actions to ensure your jobs run in the proper way, such as
-        running a brand new pipeline from scratch.
+        In GitLab 10.3, we introduce strict checking on these dependencies. Since
+        jobs will fail if their dependencies cannot be found, you'll always be aware
+        if something required is missing. This allows you to take proper actions
+        to solve the problem, for example running a brand new pipeline from scratch.
     - name: Restricted deletion of CI/CD job logs
       available_in: [ce, ees, eep]
@@ -189,7 +185,7 @@ features:
         authorized to erase the job logs; enforcing a more consistent permission
         model.
-    - name: Improved integration with existing clusters
+    - name: Improved integration with existing clusters (Beta)
       available_in: [ce, ees, eep]
       documentation_link: 'https://docs.gitlab.com/ee/user/project/clusters/'
       documentation_text: "Read through the documentation on cluster integration"
@@ -545,6 +541,25 @@ features:
         * Docker Registry has been updated to 2.6.2
         * Redis has been updated to 3.2.11
+    - name: Handling oudated replicas with database load balancing
+      available_in: [eep]
+      documentation_link: https://docs.gitlab.com/ee/administration/database_load_balancing.html
+      documentation_text: 'Read through the documentation on database load balancing'
+      reporter: yorickpeterse
+      description: |
+        The database load balancer included in GitLab Enterprise Edition has
+        been improved so it can handle replicas that are lagging behind too
+        much. This has been combined with adjustments to the replica status
+        checks to reduce the number of queries necessary to check if a replica
+        is available.
+
+        These changes allow the database load balancer to stop sending read-only
+        queries to replicas when those replicas are lagging behind with
+        replicating data from a primary.
+
+        For more information see EE merge request
+        [3526](https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3526).
+
     - name: Performance improvements
       available_in: [ce, ees, eep]
       documentation_link: https://gitlab.com/groups/gitlab-org/merge_requests?scope=all&utf8=%E2%9C%93&state=merged&label_name%5B%5D=performance&milestone_title=10.3
@@ -559,7 +574,16 @@ features:
         an instance that has over one million users!
         In GitLab 10.3 we are shipping 24 performance improvements for merge
-        requests, CI/CD, Prometheus, frontend, and a lot more!
+        requests, CI/CD, Prometheus, frontend, and a lot more! Some of the
+        noteworthy improvements include:
+
+        * [Performance of loading large / many Wiki pages has been improved](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/15276)
+        * [Search performance has been improved by adjusting search behaviour based on the number of length of the search query](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/15592)
+        * [The number of timestamp updates for issues and merge requests has been reduced](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/15682)
+        * [Redundant import status checks have been removed](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/15752)
+        * [The number of queries needed to display project atom feeds has been reduced](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/15788)
+        * [Object allocation tracking has been removed to remove the negative impact this had on performance](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/15834)
+        * [Stop sending milestone and labels for Projects::MergeRequestsController#show.json requests](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/15847)
 # MVP
 mvp:
@@ -603,6 +627,13 @@ barometer:
     from the Rails console:
     ```Sidekiq::Queue.new('background_migration').size```
+    In this release we change the local path where job artifacts are stored on disk, so if you have
+    a specific setup for that, for example a NFS mount shared between different servers, you should
+    consider to review your infrastructure in order to support the new location. Old artifacts are
+    still available in the previous location, only new ones will be affected.
+
+    The new location is [TBD].
+
 # DEPRECATIONS (optional)
 deprecations:
   - feature_name: GitLab Geo SSH repository sync

source/includes/release.html.haml

@@ -154,15 +154,15 @@
               %img{class: "shadow", :src => "#{primary_feature.image_url}", :alt => "#{primary_feature.name}"}/
 / secondary features
-%section#secodary-features.secodary-features
+%section#secodary-features
   .release-post-section.text-center.zero-bottom-margin
     %h2{:id => "other-improvements-in-gitlab"}
       %a.header-link{href: "#other-improvements-in-gitlab"}
       = "Other Improvements in GitLab #{current_article.data.release_number}"
-  - datafile.features.secondary.each_slice(2) do |secondary_feature_arr|
-    .release-row.align-top.divider
-      - secondary_feature_arr.each do |secondary_feature|
-        .column
+  .release-row.align-top.divider
+    .column
+      - datafile.features.secondary.each_with_index do |secondary_feature, i|
+        %div{ class: ("hidden-lg" unless i.even?) }
           %h3{:id => "#{secondary_feature.name.downcase.tr(" ", "-")}"}
             %a.header-link{href: "##{secondary_feature.name.downcase.tr(" ", "-")}"}
             = secondary_feature.name
@@ -200,6 +200,47 @@
                   Read through the documentation on
                   = secondary_feature.name
+    .column
+      - datafile.features.secondary.each_with_index do |secondary_feature, i|
+        - if i.odd?
+          .visible-lg
+            %h3{:id => "#{secondary_feature.name.downcase.tr(" ", "-")}"}
+              %a.header-link{href: "##{secondary_feature.name.downcase.tr(" ", "-")}"}
+              = secondary_feature.name
+              .badge-container
+                - secondary_feature.available_in.each do |available_in|
+                  - if available_in == "ce"
+                    %a{"title" => "GitLab Community Edition", "data-toggle" => "tooltip", "data-placement" => "top"}
+                      %span{class: "#{available_in}"}<
+                        = "#{available_in}"
+                  - if available_in == "ees"
+                    %a{"title" => "GitLab Enterprise Edition Starter", "data-toggle" => "tooltip", "data-placement" => "top"}
+                      %span{class: "#{available_in}"}<
+                        = "#{available_in}"
+                  - if available_in == "eep"
+                    %a{"title" => "GitLab Enterprise Edition Premium", "data-toggle" => "tooltip", "data-placement" => "top"}
+                      %span{class: "#{available_in}"}<
+                        = "#{available_in}"
+                  - if available_in == "eeu"
+                    %a{"title" => "GitLab Enterprise Edition Ultimate", "data-toggle" => "tooltip", "data-placement" => "top"}
+                      %span{class: "#{available_in}"}<
+                        = "#{available_in}"
+            = kramdown(secondary_feature.description)
+            - if secondary_feature.image_url != nil
+              - if secondary_feature.image_noshadow == true
+                %img{:src => "#{secondary_feature.image_url}", :alt => "#{secondary_feature.name}"}/
+              - else
+                %img{class: "shadow", :src => "#{secondary_feature.image_url}", :alt => "#{secondary_feature.name}"}/
+            - if secondary_feature.documentation_link != nil
+              %p
+                %i.fa.fa-book
+                %a{href: "#{secondary_feature.documentation_link}", target: "_blank"}
+                  - if secondary_feature.documentation_text
+                    = secondary_feature.documentation_text
+                  - else
+                    Read through the documentation on
+                    = secondary_feature.name
+
 / complementary information
 - if datafile.extras != nil
   %section.release-post-section

source/posts/2017-12-22-gitlab-10-3-released.html.md

@@ -26,8 +26,9 @@ GitLab 10.3 we're adding several exciting new features that help bring that
 vision to life. [Static Application Security
 Testing](#static-application-security-testing) and [Browser Performance
 Testing](#browser-performance-testing) expand the scope of your CI/CD pipeline
-with security and performance checks, respectively. And of course, as best
-practices, they're included by default with Auto DevOps.
+with security and performance checks, respectively. SAST
+has already been added as a best practice to Auto DevOps, with Browser
+Performance Testing soon to follow.
 ## Discussion and collaboration
 {:.intro-header}
@@ -51,7 +52,7 @@ project](#multiple-kubernetes-clusters-per-project-(beta)), which enables a comm
 best practice of keeping your production cluster isolated from your dev and test
 cluster(s).
-With we're shipping an enhancement to Auto DevOps. Now, when you enable
+With 10.3 we're shipping an enhancement to Auto DevOps. Now, when you enable
 Auto DevOps for your project, the [first pipeline will run automatically](#automatically-run-first-pipeline-when-enabling-auto-devops),
 without needing to trigger it manually.
@@ -67,7 +68,7 @@ Issue Boards.
 Read on to see everything that was released in GitLab 10.3!
-We thank you for helping to create great software with GitLab in 2017! We wish
+We thank you for helping us to create great software with GitLab in 2017! We wish
 you a Merry Christmas, happy holidays, and a new year full of great surprises!
 Cheers!

source/stylesheets/release-posts.css.scss

@@ -329,24 +329,3 @@ h3,
 .changelog {
   margin: 70px 0;
 }
-
-.secodary-features {
-  .release-post-section + .release-row.divider {
-    margin-top: 60px;
-  }
-
-  .release-row.divider {
-    margin-top: 0;
-
-    &:not(:last-child) {
-      margin-bottom: 0;
-    }
-  }
-
-  @media (min-width: $screen-lg-min) {
-    .release-row.divider .column {
-      margin-top: 0;
-      align-self: stretch;
-    }
-  }
-}