Skip to content
Snippets Groups Projects

Release 8.6.0

Merged Rémy Coutable requested to merge release-8-6 into master

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
15 Thanks ***MVP_USER_FIRST_NAME***!
16
17 <!--more-->
18
19 ## feature 1
20
21 > [Documentation link](link)
22
23 ## feature 2
24
25 > [Documentation link](link)
26
27 ## Other changes
28
29 This release has more improvements, including security fixes. Please check out [the Changelog](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) to see the all named changes.
30
  • Contributor

    Proposed update for GitLab Mattermost:

    GitLab Mattermost 2.1

    Mattermost 2.1 ships in GitLab 8.6 with new Android, Windows, Linux and Mac apps with full GitLab SSO support, plus Brazilian Portuguese translation and more. Mattermost 2.1 contains a security update and earlier deployments should upgrade to this version.

    Here's the raw version:

    ## GitLab Mattermost 2.1
    
    [Mattermost 2.1](http://www.mattermost.org/mattermost-2-1-android-windows-linux-and-mac-apps-plus-portuguese/) ships in GitLab 8.6 with new Android, Windows, Linux and Mac apps with full GitLab SSO support, plus Brazilian Portuguese translation and more. Mattermost 2.1 contains a [security update](http://docs.mattermost.com/administration/changelog.html#security-update) and earlier deployments should [upgrade to this version](http://doc.gitlab.com/omnibus/gitlab-mattermost/). 
  • Thanks, added!

  • Yorick Peterse Added 1 commit:

    Added 1 commit:

    • b08a2f73 - Added PostgreSQL changes to the upgrade barometer
  • I added the PostgreSQL changes to the upgrade barometer (including some steps to follow in case poop hits the fan) in commit b08a2f736ad2c4ddbe2e16d6e932c67d1d41f4ab, feel free to adjust/move around if needed.

    cc @sytses

    Edited by Job van der Voort
  • Yorick Peterse Added 1 commit:

    Added 1 commit:

    • 3758cf4d - Added PostgreSQL changes to the upgrade barometer
  • Author Developer

    Hello @All, this is the merge request for the monthly release post that will go out on the 22nd, announcing the new GitLab version. Right now it's all boilerplate, but feel free to remind us about things that shouldn't be left out!

  • Job: added. Thanks @yorickpeterse

    More performance changes that were added after I wrote my previous comment:

    Edited by Job van der Voort
  • Job: added. thanks @jschatz1

    Edited by Job van der Voort
  • External users, these can only access internal and private projects where they've been explicitly granted access to: gitlab-org/gitlab-ce!3171.

    Edited by Job van der Voort
  • New branch from an issue: gitlab-org/gitlab-ce!2808

    Edited by Job van der Voort
  • Yorick Peterse Added 1 commit:

    Added 1 commit:

    • 03e0256b - Added note about Omnibus users and pg_trgm
  • Reassigned to @JobV

  • Job van der Voort Added 444 commits:

    Added 444 commits:

  • Added 1 commit:

  • Another performance note: performance of viewing individual issues will be improved by caching certain Git operations, see https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3296 for more information.

    Edited by Job van der Voort
  • We also upgraded omniauth-saml to the latest version to add new features: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3170

    I'm not sure if it's release post worthy, though.

    Edited by Achilleas Pipinellis
  • Added 1 commit:

  • This is mostly a note for ourselves as the barometer already mentions downtime, but confidential issues (https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/227) will require downtime (in case it hasn't already been deployed) as it adds a column to the "issues" table with a default value.

    cc @marin @jnijhof @pcarranza

  • Author Developer

    @JobV Easily (un)mark merge request as WIP using link: gitlab-org/gitlab-ce!3006

    Edited by Job van der Voort
  • thanks @jacobvosmaer, appreciate that I can just c/p this!

    • We enabled HTTP caching for requests that fetch the raw contents on a single file in a Git repository. Cache times range from 1 minute (for 'mutable' resources like https://gitlab.com/gitlab-org/gitlab-ce/raw/master/VERSION which use a branch name) to 1 hour (for immutable resources like https://gitlab.com/gitlab-org/gitlab-ce/raw/17de30f412b5eddaa080006b6dd2aae2bd2d5647/VERSION that use a commit SHA). In addition to this we configured NGINX in the Omnibus packages to use up to 1 GB of disk space for proxy caching. These two changes combined reduce the load on GitLab servers that get many requests of HTTP clients polling a single file in a public repo.
    • In GitLab 8.4 we added a 'housekeeping button' to the project settings page. This button triggers a git gc run on the project. In GitLab 8.6 we have automated this button: every 10 pushes, but no more than once per hour, GitLab will run git gc on repositories. This should (slightly) improve Git disk use and performance.
    Edited by Job van der Voort
  • @JobV

    We removed download_url from Builds API. We decided to do that, because it referred to controller action, which requires normal user login. This seems redundant, because we provide an API for downloading artifacts for specific build: http://doc.gitlab.com/ce/api/builds.html#get-build-artifacts.

    Edited by Job van der Voort
  • @JobV Issue move to another project https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/2831, will get merged today probably.

    Edited by Job van der Voort
  • @JobV

    We need to let the people know that we faced the problem of the tcp connection being dropped while running the migration to generate the trigram indexes.

    operations#135 (closed)

    cc/ @yorickpeterse @jnijhof @marin

    Edited by Achilleas Pipinellis
  • Rémy Coutable Added 1 commit:

    Added 1 commit:

  • Added 1 commit:

  • Added 1 commit:

  • Add a note about the new LDAPGroupSync worker. We split LDAPSyncworker and LDAPGroupSync worker. Performance will be greatly improved for large installations. If you want to provide details: It runs once per hour. In our benchmark runs, for 20,000 users and 10,000 groups, the sync takes 15 minutes. This is in contrast to hours or, in extreme cases, 1-2 days for the old LDAPSyncWorker (which synced groups, too).

    Edited by Job van der Voort
  • Added 1 commit:

  • Added 1 commit:

    • 7587ce0d - highlight performance improvements
  • Added 1 commit:

    • ed9f9206 - ldap performance improvements
  • @JobV Wanted GIFs for:

    1. new dropdowns, especially the issues list one where you can make a new label and all
    2. labels select in sidebar
    3. anything else you can think of
    4. Todos with JS
    5. move issue to another project
    1. Here's creating a label. I'm unsure about using it because the button gets cut off (already opened an issue to fix):

      create-label-from-dropdown

    2. As far as I can tell, label multi-select did not make it into 8.6 -- @jschatz1?

    3. ¯\_(ツ)_/¯

    4. fast-todos

    5. Hard to show this well in a GIF I think. I'll try.

    Edited by Robert Speicher
  • Job: added

    Geo features:

    • OAuth authentication
    • Wiki synchronization
    • SSH keys synchronization

    We should recommend any one trying Geo to use 8.6

    Edited by Job van der Voort
  • Group visibility level: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3323 Like with projects, the visibility of a group can be set to dictate whether anonymous users, all signed in users, or only explicit group members can view it. The restriction for visibility levels on the application setting level also applies to groups, so if that's set to internal, the explore page will be empty for anonymous users. The group page now has a visibility level icon. Solves this popular issue: https://gitlab.com/gitlab-org/gitlab-ce/issues/12658

    Edited by Job van der Voort
  • Added 1 commit:

  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Please register or sign in to reply
    Loading