Gitlab 10.7 Released • Hacker News Board

Re: Gitlab 10.7 Released

#81

Post by jchw » Mon, Apr 23, 2018, 10:30 PM UTC

jbk wrote: post #27

sytse wrote: post #23

Earlier quoted context omitted.

Awesome that your upgrades are smooth, thanks for posting. We're indeed a completely remote team, see https://about.gitlab.com/culture/remote-only/ And we do want to make sure that all the features you really need are there. I understand the VideoLan needs https://gitlab.com/gitlab-org/gitlab-ce/issues/40321 and we're prioritizing it.

> We're indeed a completely remote team, see https://about.gitlab.com/culture/remote-only/ That's very hard to keep at a constant pace. > And we do want to make sure that all the features you really need are there. So far, everything is great, but we would love to have: - Custom Fields, in order to leave trac (such a pain, this service is); - A way to fork/MR across Gitlab/Github instances: we don't want our instance…

>- Be able to update a MR without push-forcing on the same branch, but with a new branch (that allows better reviewing of older versions).

Although not identical, it's worth noting that GitLab tracks all versions of MRs throughout the life of an MR. So, if you force push, you can compare the MR before and after the force push, via the "Changes" tab. I could be wrong, but I believe this is actually a leg up on what GitHub provides.

Re: Gitlab 10.7 Released

#82

Post by theptip » Tue, Apr 24, 2018, 5:44 PM UTC

joshlambert wrote: post #32

theptip wrote: post #13

Rather comically, I've been unable to import my Gitlab.com repo into an on-prem Gitlab EE instance for the last 3-4 months, due to an import bug -- seems like that's the one import that should be easy to test thoroughly, but apparently not. Here's to hoping that this version happens to have fixed the issue!

Thanks for the report @theptip. Did you happen to open an issue? It would be great to ensure this one is being tracked appropriately.

I opened tickets with GitLab support, which were eventually closed due to inactivity (i.e. support let the issues time out without a resolution, despite me doing two 1-hour live debugging sessions with a support rep and a full stack trace highlighting the failing code).

In general I wasn't expecting to have to raise issues on the open source tracker myself after reporting to internal/paid support, but perhaps that's where I went wrong.

Re: Gitlab 10.7 Released

#83

Post by mosh6 » Tue, Apr 24, 2018, 8:38 PM UTC

tenaciousDaniel wrote: post #57

transmit101 wrote: post #8

I implemented the HTTPS-only Pages feature in this release. I just wanted to say that GitLab is a great project to contribute to, with a very friendly and professional community! Definitely recommend to anybody interested in contributing to a project themselves. [1] https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/16273 [2] https://about.gitlab.com/contributing/

We switched over to Gitlab from Stash about 9 months ago and it's been fantastic. There are so many amazing features, and the CI/CD integration has been smooth. I highly recommend it.

What features you have in gitlab that you couldn't find on bitbucket / stash ?

Re: Gitlab 10.7 Released

#84

Post by lbotos » Tue, Apr 24, 2018, 10:51 PM UTC

theptip wrote: post #82

joshlambert wrote: post #32

Earlier quoted context omitted.

Thanks for the report @theptip. Did you happen to open an issue? It would be great to ensure this one is being tracked appropriately.

I opened tickets with GitLab support, which were eventually closed due to inactivity (i.e. support let the issues time out without a resolution, despite me doing two 1-hour live debugging sessions with a support rep and a full stack trace highlighting the failing code). In general I wasn't expecting to have to raise issues on the open source tracker myself after reporting to internal/paid support, but perhaps that's…

I'm working this quarter to help improve our quality of service. If you email me the ticket number(s) at lee@gitlab.com I'm happy to dive in and take a look. In theory, if we had clear traces an issue should have been made on your behalf. Happy to help get to the bottom of this.