[rohanprabhu]

Kind of off-topic, but the work GitLab is putting in and the things they come up with every other day is crazily impressive. We moved from Github to GitLab sometime ago and we believed that to be a trade-off for moving to our own infrastructure. It always seemed like GitLab wasn't "quite there". Today, however it is a whole different story. We pretty much cannot go back to Github at all because of how well-integrated, stable and beautiful this product is.

[jobvandervoort]

Thanks. That's really great to hear!

Although we still have ways to go, we recently made large strides in terms of performance and UX. Two areas we know we were lacking in, in the past.

I'd love to hear what we can improve further.

[asimuvPR]

This is super nice. After the "Dear Github" letter I moved to gitlab and have not looked back. Its great to see this project grow in a manner that respect the community that adopts it.

[sytse]

Thanks asimuvPR! BTW For our 'Dear Open Source Maintainers' letter please see https://about.gitlab.com/2016/01/15/making-gitlab-better-for...

[asimuvPR]

I'm very aware of it. :)

Do you mind if I email you?

[sytse]

Of course not, http://sytse.com/ has my personal email.

[rohanprabhu]

Just my 2 cents, but how gitlab has constantly improved over all other features, I would really love to see issues get the same treatment. The current issues system is simple, easy to use and works fine but we really didn't find it to be scalable when moving to bigger teams. Labels as a primitive method of categorization is fine, but it very soon becomes unmanageable. Getting to a feature set like JIRA is too much to ask I guess, but a middle ground would really help keep everything in gitlab.

[exabrial]

Stability, it's made leaps and bounds in the last 9 months, but every time you push a new feature make sure it "just works" and doesn't break other things. Thanks!

[sytse]

Good to hear we got more stable of the last 9 months. I'm excited about the upcoming release (the 22nd as usual) that will have many UX improvements and bugfixes. We try to ship new features fast and quickly fix issues that arise. But we're not happy with our testing of core functionality. So today I discussed writing more end-to-end tests as proposed by our new VP of Product, Stan Hu.

[StavrosK]

Seriously, we evaluated it, what, two months ago, and it was missing some features. I check now, and it has the missing features and then some. I wonder if we were just evaluating Community edition and it didn't have merge requests or something...

I am super impressed with Gitlab, though. I am moving projects there right now.

[sytse]

The Community Edition also has merge requests and all the major and essential features. For the feature differences please see https://about.gitlab.com/features/#compare

[StavrosK]

Yep, I saw that page after I commented. Looks fantastic, I'm loving the super easy CI integration.

[sytse]

Glad to hear that!

[jobvandervoort]

That's great to hear. Let us know if you need any help moving or get stuck somewhere.

[StavrosK]

Will do, I'm going to push for us to switch to you guys. What's currently our biggest hurdle is this issue:

https://gitlab.com/gitlab-org/gitlab-ce/issues/989

Which makes a label system really hard to use (it's basically half-implemented without that feature).

And a cosmetic feature request I filed:

https://gitlab.com/gitlab-org/gitlab-ce/issues/15409

[jobvandervoort]

Awesome, great to hear.

Multi-label filter is coming this friday to GitLab 8.7!

The other issue will also be solved in a future release, I'll reply in detail there.