Live data from Hacker News

GitLab 8.5 released

about.gitlab.com

241–246 of 246 posts

Re: GitLab 8.5 released

#241
post #233
post #141

Earlier quoted context omitted.

Glad you like our WIP function. Do you maybe have any suggestions how we can make navigation better and/or examples of pages where you are missing information?

The decision of what does and doesn't go in the sidebar is very non-intuitive (sometimes what I want is in the sidebar but sometimes it's in the main page). For example, in groups and user profiles you can find the list of projects in the main body of the page (and it's not visible immediately). Why is it not in the sidebar if you have a sidebar? And then the ordering is also a bit weird -- I don't think many people…

Thank you for your feedback.

> The decision of what does and doesn't go in the sidebar is very non-intuitive

We try to put top level navigation into sidebar and everything else in the main page. For example navigation to `Projects` is in sidebar however tabs to switch between starred projects or personal projects is in main body.

> For example, in groups and user profiles you can find the list of projects in the main body of the page (and it's not visible immediately). Why is it not in the sidebar if you have a sidebar?

Good example. Agree its still non-intuitive in some places. For you particular example we created an issue to fix - https://gitlab.com/gitlab-org/gitlab-ce/issues/13480.

> And then the ordering is also a bit weird -- I don't think many people would consider the order in GitLab to be "in order of importance" or even "regular use"

Ordering of projects is either by last activity or alphabetically. But in any case there is usually a dropdown in UI to sort by other criteria.

> And why can't I see the set of files in the repo when I first open it?

You can set what to see first at https://gitlab.com/profile/preferences page. We believe README is something people would like to see first we allow users to set different default page based on their preferences.

P.S. Thank you very much for your feedback. It will help us make GitLab UI more intuitive.

Re: GitLab 8.5 released

#242
post #57

Earlier quoted context omitted.

It is extremely slow. We tried it on a 1go droplet and it felt slow with 2 users but can't beat that £0 price.

Have you tried running GitHub EE on something of the same spec? It's terrible to near impossible and it doesn't include nearly as many of the features as Gitlab. We have been running Gitlab for 100~ employees for well over a year on a single, medium/low specced VM and its lightning quick, so much so that when Devs/Ops have to use GitHub you can hear the sighs around the office!

> medium/low specced VM

Can you be more specific? Does that mean 1core+512MB? Is 8core+12GB considered medium to you? Is that 100 Programmers or 50 Programmers plus 50 issue commented?

Totally agree on GHEE. I have 4 Programmers+4commenters running on a $200/month recommended hosting partner and it's performance is not up to my expectations (especially when I'm the only one on...)

Re: GitLab 8.5 released

#243
post #142

Earlier quoted context omitted.

I agree we can do a lot better in project discovery on GitLab.com. I do want to mention that https://gitlab.com/explore?utf8=%E2%9C%93&filter_projects=gi... gives results in a few seconds and GitLab itself is the first hit.

Issue search has a lot of room for improvement. All terms in the search query must occur consecutively.

Totally agree, I hope it will get better after we enable Elastic Search on GitLab.com in a few days.

Re: GitLab 8.5 released

#244
post #81
post #63

Earlier quoted context omitted.

Indeed. The search field is currently only displayed for users that have logged in.

Thanks, that doesn't make sense so I made an issue to remedy it https://gitlab.com/gitlab-org/gitlab-ce/issues/13676

Update: we'll ship this fix with 8.6. It has just been merged.

Re: GitLab 8.5 released

#245

Earlier quoted context omitted.

It's so funny that this is the way it's become, as Atlassian grew up being the cheaper, simpler alternative to extremely expensive, super opaque, ultra closed source systems like Clear Case. I remember a time when Atlassian actually raised the prices of Jira's top level of support and service because enterprise CTOs were confused by such a low price point.

Ten years ago I made exactly this migration for a SaaS shop's helpdesk & dev team. At the time JIRA was easily the best value & most customisable solution for integrated ticket tracking. I learned Java & Groovy to write extensions for it. It wasn't just CTO/CIO friendly, JIRA really was the great choice at the time in both UX and ease of implementation. Especially if you'd been bogged down hacking RT or GNATS or perm…

> I learned Java & Groovy to write extensions for it

For the last 3 months, Groovy has been officially known as "Apache Groovy".

Post reply on HN