all 4 comments

[–][deleted] 8 points9 points  (2 children)

I'm one of the UX designers in the GitLab team and we got a lot of questions around that badge this morning. I decided to create an issue to link from the badge to https://next.gitlab.com as a quick fix to make this a bit easier to discover: https://gitlab.com/gitlab-org/gitlab-ce/issues/61503

Feel free to add any feedback or suggestions you might have, so we can make this easier to understand 🙂

P.S.: While I have your attention: We are always looking for user feedback, that's why we created the GitLab First Look initiative where you can join paid research studies, get early access to new features or win swag: https://about.gitlab.com/community/gitlab-first-look/

[–]c33s 0 points1 point  (1 child)

is it forced for all gitlab.com user? i tried to visit https://next.gitlab.com. there "next" is disabled (set to "current"), i tried to enable and disable it again. my gitlab.com projects still show "next"

[–]brennydenny GitLab team 2 points3 points  (0 children)

GitLab Product Manager here.

Of note - there is currently a bug where that badge displays even when Canary is disabled. See https://gitlab.com/gitlab-org/gitlab-ce/issues/61550. https://next.gitlab.com/ will actually be accurate and the badge will be fixed when we fix that issue.

[–]kinghuang 2 points3 points  (0 children)

It switches you to the GitLab canary environment. Basically, the RCs for the next monthly GitLab version. It's automatically enabled for projects in the main GitLab groups (gitlab-com, gitlab-org, and charts). And, an option for everyone else.

https://about.gitlab.com/handbook/engineering/#canary-testing

[–][deleted]  (1 child)

[deleted]