[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.