GitLab 7.4 regressions

This is a meta issue to discuss possible regressions in this monthly release and any patch versions. Please do not raise issues directly in this issue but link to issues that might warrant a patch release. The decision to create a patch release or not is with the release manager who is assigned to this issue. The release manager will comment here about the plans for patch releases.

/cc @JobV @dzaporozhets @jacobvosmaer @marin @sytses

This PR should go into 7.4. It's fixing a regression introduced in 7.4.

This one probably: https://github.com/gitlabhq/gitlabhq/issues/8090

Edit by Marin: Confirmed and fixed.

This one probably: https://github.com/gitlabhq/gitlabhq/issues/8083

Milestone changed to 7.4

Internal issue (500 on project filter in admin): https://dev.gitlab.org/gitlab/gitlabhq/issues/1693

NOTE: Not specific to 7.4

This one: https://gitlab.com/gitlab-org/gitlab-ce/issues/699

@vsizov Can you strike-through (with ~~) already addressed issues

EDIT by Marin: Fixed.

This one: https://gitlab.com/gitlab-org/gitlab-ce/issues/700

EDIT by Marin: Not a regression as the person didn't checkout the rc1 tag. GitLab 7.4 is incompatible with gitlab-shell 2.0.1

Many upgrade documentation issues:

• https://github.com/gitlabhq/gitlabhq/pull/8072
• https://github.com/gitlabhq/gitlabhq/pull/8071
• https://github.com/gitlabhq/gitlabhq/pull/8070
• https://github.com/gitlabhq/gitlabhq/pull/8069
• https://github.com/gitlabhq/gitlabhq/pull/8068
• https://github.com/gitlabhq/gitlabhq/pull/8067
• https://github.com/gitlabhq/gitlabhq/pull/8066
• https://github.com/gitlabhq/gitlabhq/pull/8065
• https://github.com/gitlabhq/gitlabhq/pull/8064

This one: https://github.com/gitlabhq/gitlabhq/issues/8115

@vsizov Could you combine this PRs to one and make it to master so that @vsizov cherry-pick it? @vsizov Is that the right workflow?

This one: https://gitlab.com/gitlab-org/gitlab-ce/issues/701

Edit by Marin: Confirmed and fixed.

This is maybe related to the LDAP refactoring: https://github.com/gitlabhq/gitlabhq/issues/8129

This maybe: https://github.com/gitlabhq/gitlabhq/issues/8135

And #704 (closed)

mentioned in issue #704 (closed)

mentioned in issue #704 (closed)

Patch release 7.4.1 will be tomorrow

Patch release will fix: git over http for LDAP users, public snippets, submodules 500 error

public snippets is still not resolved, see my comments in #704 (closed)

Thanks @arif-ali we are looking into it.

We have updated the 7.4.0/7.4.1 blog posts https://gitlab.com/gitlab-com/www-gitlab-com/commit/b6fe6df416294f33c134e5f8d08f5427d858a1e8

7.4.2 released https://about.gitlab.com/2014/10/24/gitlab-7-4-2-released/

@vsizov, I've mentioned another issue in #704 (closed) with the public snippets, not sure if you have seen that

@arif-ali The issue is fixed in master.

@vsizov There is an interesting report in the blog post https://about.gitlab.com/2014/10/30/gitlab-7-4-3-released/#comment-1661534210

@sytses I don't if that's the same guy but someone opened this issue https://gitlab.com/gitlab-org/gitlab-ce/issues/756

I replied that we released new packages, I think he caught an old package somehow.

@JobV is right. First packages were broken but they have not been published. I think this guy caught package directly from amazon. This bug was fixed by 353a9875

MergeReq list of commitIDs/Compare View list of commitIDs becomes inaccurate - regression reported at https://github.com/gitlabhq/gitlabhq/issues/8174. We started seeing this issue after moving from 7.3 to 7.4.2. Also reported by two other users in same issue.

Possibly related to a5d23ae3

Looks like https://github.com/gitlabhq/gitlabhq/issues/8174 was caused by a regression in Rugged from 0.19 to 0.21 -- moving to 0.21.1b2 has resolved this issue for us. Please consider for GitLab 7.5.

Thanks for pointing this out @sroth80021 . We are going to look into rugged 0.21.1b2 but it is too close to release day to be putting this into 7-5-stable. Especially in light of the warnings about API incompatibility in https://github.com/libgit2/rugged/issues/431.

Closing this since 7.4 already released.

Status changed to closed