john_cogs

I lead the Developer Evangelism team at GitLab.

Oh, maybe we should add a "Jump to Key Features" button up top. Thanks for the idea!

Thanks for the feedback.

This is the first time we wrote a blog post about a release in addition to the release post we publish each month on the 22nd. (The release post for 14.0 can be found here: https://about.gitlab.com/releases/2021/06/22/gitlab-14-0-rel...)

We'll keep iterating to make these blog posts more appealing to the wider community in the future.

For more detail on what's new in the 14.0 release, you can find the release post here: https://about.gitlab.com/releases/2021/06/22/gitlab-14-0-rel...

GitLab provides issues, boards, epics, time tracking, road maps, and more as part of the Plan stage: https://about.gitlab.com/stages-devops-lifecycle/plan/

GitLab team member here. Thanks for sharing!

We also wrote a blog post about GitLab 14: https://about.gitlab.com/blog/2021/06/22/gitlab-14-modern-de...

One thing I'd like to highlight from the blog: "Thanks to GitLab’s open core model, more than 10,000 merge requests from the wider community have been merged into the product since January 2016."

Thanks to all the community members who have made this milestone release possible!

This page in the GitLab handbook explains our approach in great detail: https://about.gitlab.com/company/stewardship/

You may also want to check out this video of our founder/CEO Sid discussing commercial open source strategies: https://www.heavybit.com/library/video/commercial-open-sourc...

To do this in GitLab, click the permalink button before copying the line.

I'm going to share the feedback on page density, colors, and actions with our team.

To copy a link to a line of code, you can hover over the number next to the line of code and then copy a link to that line.

I created a gif to show what I mean: https://gitlab.com/johncoghlan/blog/-/raw/master/images/perm...

Yes, you can. Docs here: https://docs.gitlab.com/ee/ci/ci_cd_for_external_repos/githu...

Hey, GitLab team member here.

Through our startup program, we offer a free one year Ultimate license to members of the current or two most recent YC batches with less than $3M in funding. More info here: https://about.gitlab.com/solutions/startups/

If you don't meet the criteria, you can still test our Ultimate tier through a free trial: https://about.gitlab.com/free-trial/

I think you'll find there is a lot of value there for a startup that wants to focus on delivering value to their customers (rather than managing a complex toolchain).

We also have free SaaS and self-managed offerings that are available to everyone and are widely used by organizations of all sizes.

Thanks for mentioning GitLab. We're really proud of our handbook.

For folks that are exploring how to start building their own handbook, this page in might be a good place to start: https://about.gitlab.com/company/culture/all-remote/handbook...

We didn't capture that information but I've asked the person who runs the survey to consider including a question on this in next year's survey.

In the report, you'll find detail on the breakdown of the 75% number that is mentioned in the blog post:

- 25% of respondents use bots to test their code

- 16% use AI/ML to review code before a human sees it

- 34% are exploring the idea of AI/ML

You can download the full report here: https://about.gitlab.com/developer-survey/

Some highlights from the release:

- GitLab Kubernetes Agent is available on GitLab.com

- On-call schedule management

- Compliance pipelines

- Lots of improvements to pipeline efficiency

This page details GitLab's architecture: https://docs.gitlab.com/ee/development/architecture.html

On that page you'll find a link to docs for Gitaly, a Git RPC service that handles all Git calls made by GitLab.

When the tiering of a feature is being evaluated, the stewardship promise (https://about.gitlab.com/company/stewardship/#promises) will override the guidance on our pricing page (https://about.gitlab.com/company/pricing/#buyer-based-tierin...).

Thanks again for the question.

Edit - I've created an MR to document this on our pricing model page: https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_request...

The author wrote a blog post about a project GitLab is working on to shine more light on the work that is being done. While the tone and content of the post needed to be better, as we have acknowledged in both comments and changes to the post, we did receive feedback that can help us improve this project going forward.

We're also going to learn from this and improve how we write blog posts in the future, too.

To address your last point, I want to be clear that the author is a valued member of my team. His hard work has been recognized repeatedly in recent weeks in the form of awards and other recognition. This blog post will not change the high regard I, and his other colleagues, hold him in.

Everything you have seen today is our team living up to its values: the author's bias for action in publishing this post, the transparency and being quick to say sorry in how we responded and addressed this community's feedback, and how our team assumed positive intent and worked together to try to improve and learn from this situation.

You can read more about our values here: https://about.gitlab.com/handbook/values/

Thanks for the feedback. I agree.

The documentation might help you to better understand what we're building: https://gitlab.com/gitlab-org/5-minute-production-app/deploy...

Thanks for the question. I shared it with @sytse and he's putting some thought into it.

When using merge requests, each push to a branch creates a new version. You can then compare between any two versions and review the diff.

Documentation: https://docs.gitlab.com/ee/user/project/merge_requests/versi...

We use buyer based tiering to decide which tier a feature will reside in.

https://about.gitlab.com/handbook/ceo/pricing/#buyer-based-t...

Have you seen the Roadmap feature? It may be applicable to your use case.

https://docs.gitlab.com/ee/user/group/roadmap/

All new features target Free/Premium/Ultimate. Starter customer are still getting new features, improvements and fixes — they are the same features that are also available on the Free tier. For Starter customers who elected to upgrade to Premium for free, they will also have access to the new Premium features.

GitLab team member here. Thanks for this comment! I just shared on our team Slack.

Happy to answer questions on this one.

Signed, GitLab team member

Yes, you can have multiple reviewers.

This is a feed for our monthly release posts: https://about.gitlab.com/releases.xml