7.13 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 @all
Activity
This one is not regression but is pretty bad - https://gitlab.com/gitlab-org/gitlab-ce/issues/1993. Can we fix it before release?
vsizov: It has been merged to stable by @dzaporozhets and reverted again because of https://gitlab.com/gitlab-org/gitlab-ce/issues/2016
vsizov: UPDATE: Then was fixed again, so it goes to rc4
#2002 (closed) The filebrowser generates an invalid link when selecting one linerspeicher: Fix merged.
vsizov: ported to stable(in rc3)
#2001 (closed) There is no ability to change assignee of MR
vsizov: Fixed. Will go to rc4
Proposed fix for #2002 (closed) in !988 (merged).rspeicher: Merged!
vsizov: already in stable (rc3)
-
Incorrect color preview themes showing up in notes: #2008 (closed). Proposed fix in !994 (merged).vsizov: merged and ported to stable (rc3)
-
New home page includes redundant last push event: #2009 (closed). Proposed fix in !995 (merged).vsizov: merged and will be in rc4
I'll create rc3 today. List of commits to cherry-pick to stable:
-
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/986 will be reverted in stable. Or should be fixed ASAP because of https://gitlab.com/gitlab-org/gitlab-ce/issues/2016
Public project activity page asks for sign-in #2021 (closed)
vsizov: will be in rc4
@vsizov I suggest that you edit the comments to show that certain items where merged to stable and/or released in a certain RC, I think it is better for the overview than a list of hashes.
vsizov: none of developers could reproduce it
-
@sytses agree.
-
@dblessing We don't know if this is a regression issue (#2014 (closed)) because none of developers could reproduce it.
@vsizov Yes, I agree. I couldn't reproduce either. I'm OK with removing it from this list.
-
The cache improvement will be back in stable(rc4) after the fix provided by @stanhu https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/1005
/cc @dzaporozhets
-
https://gitlab.com/gitlab-org/gitlab-ce/issues/2024 will be in rc4 as well
I was able to reproduce #2014 (closed) on gitlab.com. You can see it in the history of my ticket #2005 (closed). The last comment was made using the "Comment & Close" button but it only closed the issue rather than submitting the comment.
vsizov: Developers were not able to reproduce it.
#2027 (closed) Issue's edit time is updated by new notes
vsizov: The commit that causes it (fbdaf0e2) will be reverted from 7.13 (rc4). I hope it will be improved until 7.14.
Backup fails to overwrite database.sql.gz created by aborted previous backup !1011 (merged)
vsizov: goes to rc4
-
#2027 (closed) is discussing now, and taking into account that they are not that important, I'm working on rc4 (hopefully the last one)
vsizov: reverted the commit that causes that bug. (rc4)
Group/project references are linked incorrectly because comments are cached based on first user who views it: #2033 (closed)
vsizov: goes to 7.13.1
"Create Merge Request" isn't always shown in event for newly pushed branch: #2034 (closed)
vsizov: Will be included to 7.13.1
-
!1015 (merged) documentation (You need to store your DB encryption key)
vsizov: Will be included to 7.13.1
#2043 (closed) Labels added after issue creation are not shown in the issue list.
vsizov: Will be included to 7.13.1
MR "Remove source-branch" doesn't work when source branch is in the same project #2049 (closed)
vsizov: Will be included to 7.13.1
#2048 (closed) Label modifications are not reflected in existing notes and in the issue list
vsizov: Will be included to 7.13.1
#2051 (closed) In EE, MR "Rebase before merge" doesn't work when source branch is in the same project
vsizov: Will be included to 7.13.1
-
7.12 accidentally included
session_expire_delaycolumn inschema.rb, causing a migration in 7.13 to fail in some cases. #2052 (closed)vsizov: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/1029
#2055 (closed) - 2FA documentation leads to 404
Fix in !1026 (merged)
vsizov: Will be included to 7.13.1
Great job @vsizov
-
7.13.1 is released https://about.gitlab.com/2015/07/23/gitlab-7-dot-13-dot-1-released/
#2058 (closed) - Reporter, Developer and Master roles are unable to set assignee or milestone on merge requests.
Fixed by !1037 (merged)
vsizov: Will be included to 7.13.2
-
#2092 (closed) Issues deactivated => no labels / assignee / milestone for the merge requests
rspeicher: !1042 (merged)
vsizov: Will be included to 7.13.2
-
Users hit Error 500 when navigating to a project home: https://github.com/gitlabhq/gitlabhq/issues/9484
Proposed fix in !1041 (merged)
vsizov: Will be included to 7.13.2
#2013 (closed) - MergeRequests#new does not show the first tab (Commits) automatically
Fixed by !997 (merged) (already merged, needs to be included in 7.13.2)
vsizov: Will be included to 7.13.2
It seems like the UI is broken for a user after upgrading to 7.13. Here's more information https://gitlab.com/gitlab-com/support-forum/issues/252
!1040 (merged) Rake task to update commit count (under discussion)
Not a regression but related to a 7.13 change.
vsizov: Will be included to 7.13.2
For EE, don't resend admin email to everyone if one delivery fails: https://dev.gitlab.org/gitlab/gitlab-ee/merge_requests/462 (Internal MR, sorry)
vsizov: Will be included to 7.13.3 if there will be a few more issues.
For EE, fix for GitHub Enterprise Importer: https://dev.gitlab.org/gitlab/gitlab-ee/issues/333 https://dev.gitlab.org/gitlab/gitlab-ee/merge_requests/473
vsizov: Will be included to 7.13.5 if there will be a few more issues.
-
This fixes post-receive hooks execution when use web editor or merge: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/1127
vsizov: As we discussed with @dzaporozhets it's not needed anymore.
@vsizov Thanks for being release manager, well done!
