Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitLab 8.15 Released

about.gitlab.com

Post reply on HN
Print view View original

101–110 of 117 posts

Re: GitLab 8.15 Released

#101

Post by jcordz »

eugeneionesco wrote: post #99
jcordz wrote: post #98

Earlier quoted context omitted.

Hi, thank you for bringing this to our attention. If you wouldn't mind getting in touch with Mitchell (commented below) or myself at jennifer [at] gitlab [.] com, we can look at your particular situation. To share a little background, our marketing automation system does have a limit to the number of emails a person can receive: max of 2 per day; 5 per seven days; and no limit to operational emails. Operational email…

What can Gitlab possibly mail me 5 times per week? I don't understand why this is not max 5 times per month.

Thank you for your feedback. We work very hard not to bombard the community with messages and actively work to balance our marketing, information, education and operational emails.

The 5 emails per seven day limit is not something we expect to ever utilize but allows for flexibility in our communication strategy.

Re: GitLab 8.15 Released

#102

Post by jasonkratz »

softinio wrote: post #32
kaishiro wrote: post #31

Earlier quoted context omitted.

I'm curious what kind of spam you were receiving. I'm not sure I've ever received unsolicited email from them.

Marketing stuff. And I am not against them marketing their features but it should have had an unsubscribe button and sent in moderation in my opinion. Interesting that I get downvoted for giving honest feedback. I would have thought it would help them improve seeing how different marketing ideas impact their users.

Or maybe downvoted because they do have an unsubscribe link? Every email I receive from GitLab has an unsubscribe link at the bottom.

Re: GitLab 8.15 Released

#104

Post by tomsthumb »

cryptarch wrote: post #92
tomsthumb wrote: post #68

Earlier quoted context omitted.

We run gitlab and the full config is 57 lines. A little more than half of those are comments or blank lines. This includes email and oauth. I would suggest not unbundling.

They could do both? Offer the separate parts in an easy-to-use way, and have the bundle re-use those parts.

Unless you're just super pressed for resources I'm not sure why you wouldn't just install the omnibus then disable the services you don't want.

Re: GitLab 8.15 Released

#105

Post by sverhagen »

connorshea wrote: post #18
contingencies wrote: post #17

@Gitlab: The features are great but the interface setup is shocking. That whole video assumes you have a K-cluster going already, and is a maze of this-thing, that-thing, auth-thing, copy-thing, etc. Have you guys ever tried interviewing users who are new or maintaining a Gitlab instance over major version upgrades? It's painful. The 'quick fix' for setup these days is supposed to be to use a docker image... but the…

Thanks for the honest feedback, it's genuinely useful for improving the product. Out of curiosity, why use the Docker image over our Omnibus package? Omnibus is generally what we recommend, but if that's not good enough we'd love to know how it can be improved.

We recently revamped our in-house deployment process of GitLab, and while we are certainly addicted to Docker Kool-Aid, the Docker image for GitLab just didn't do it for us. This is a few months ago, so my specifics would be a little rusty, but I remember it simply not working, spam-logging errors that didn't help me, and personally I find Docker images that try to run many-multiple applications inside a non-preferred design anyway. Contrasting that, the Omnibus installation worked absolutely without a glitch, so we went with that. Loving GitLab, though!

Re: GitLab 8.15 Released

#106

Post by mrmondo »

sytse wrote: post #84
mrmondo wrote: post #67

Plan meets final execution, love it guys and gals, great work yet again, we upgraded today without a hitch, within 30 minutes I had devs making positive comments in chat about the upgrade. Thank you again for all your hard work and the passion that drives that.

Thanks for leaving a comment Sam. Glad to hear the upgrade went smooth and people are happy. People that experience problems are more likely to let us know about it so we greatly appreciate your comment.

and just upgraded to 8.15.1 flawlessly :)

Re: GitLab 8.15 Released

#107

Post by mrmondo »

anhtran wrote: post #87

Gitlab has too many downtimes for upgrading. When I got a failed push I was saying: Oh gitlab has a new version... :meh:

We have a great deal of repos on our GitLab private server and even a major upgrade only results in 2 minutes or so of downtime.

What spec hardware are you running this on?

Re: GitLab 8.15 Released

#108

Post by hackerboos »

ksec wrote: post #85

This may be a silly question. How did Github manage to burn 66M a year while Gitlab manage to be open source, offer an Free GitLab.com Hosting and continue a Rapid pace of improvement in multiple domain?

They got fat and lazy. The competition wasn't there previously. Bitbucket, Gitorious etc just weren't up to scratch so Github was a defacto monopoly for cloud hosting of git repositories.

The gitlab came on the scene, shipped a Github replacement and then some. Is shipping features in 6 months faster than Github did over the past few years.

Github have woken up though and started shipping features again.

It's good to have competition. At least, for consumers.

Re: GitLab 8.15 Released

#109

Post by elygre »

contingencies wrote: post #78
sytse wrote: post #62

Earlier quoted context omitted.

The image Cidan referred to was last pushed 5 hours ago when we released 8.15 and should always be up to date. For more information about our official docker images see https://docs.gitlab.com/omnibus/docker/README.html I've added a section to say that these images are officially supported with https://gitlab.com/gitlab-org/omnibus-gitlab/commit/26501d91... If you experience problems with them please feel free to fil…

should always be up to date OK. I definitely remember running in to something that looked official but wasn't up to date (remotely) a few weeks ago. Perhaps it was this image, perhaps not. IIRC at the time I was judging only from the 'updated [time periods] ago' data in the docker hub webpages.

If someone gave me a bug report along the lines of "the image didn't work, but I don't remember which image it was", it would be ... bad.

Re: GitLab 8.15 Released

#110

Post by sytse »

jcordz wrote: post #98
softinio wrote: post #30

I recently registered to try gitlab. I received unprecedented large amounts of spam from them daily with no unsubscribe button. I finally emailed them to stop the spam and they did but not completely I received more but had unsubscribe this time. Unsubscribed so lets see what happens. One more spam and I will close my account and never try them again GitHub is great, does the job incredibly well, doesn't get in the w…

Hi, thank you for bringing this to our attention. If you wouldn't mind getting in touch with Mitchell (commented below) or myself at jennifer [at] gitlab [.] com, we can look at your particular situation. To share a little background, our marketing automation system does have a limit to the number of emails a person can receive: max of 2 per day; 5 per seven days; and no limit to operational emails. Operational email…

We decided we should look into improving it, you can follow our progress in https://gitlab.com/gitlab-com/marketing/issues/740
Post reply on HN