Skip to content
This repository has been archived by the owner on Aug 30, 2023. It is now read-only.

Is Master Stable for Production? #177

Closed
pacarvalho opened this issue Mar 20, 2018 · 4 comments
Closed

Is Master Stable for Production? #177

pacarvalho opened this issue Mar 20, 2018 · 4 comments

Comments

@pacarvalho
Copy link

Is the current master branch or any of other branches stable enough for use in a production environment? Are there plans for releasing a production version soon?

@mbyio
Copy link

mbyio commented May 8, 2018

I'm also wondering this. It actually seems pretty unstable. Eg. in #185 they merged a PR without actually knowing what it does. And in may PRs or issues, nobody from Sentry has even bothered to respond.

@mattrobenolt
Copy link
Contributor

It's stable and people use it. In #185, there was some background that wasn't discussed on GitHub. Yes, I don't truly know what's going on, but it's not particularly important. I trust the person with the patch. They are using some tooling that I don't have personal experience with, so I don't have any strong opinions.

As for unaddressed PRs and issues, this is really hard for us right now. At the moment, we don't have a dedicated person on our team for raven-go. Go isn't used very heavily on our platform at the moment. I am the only one who even pokes at issues, while I don't write Go for my job anymore. I use it for side projects, but it's not a big part of my day to day anymore.

With that said, there's a reason why PRs sit open and issues unaddressed, because I'm not as comfortable merging them since I don't have the ability to commit the time needed to make sure they're correct and stable because I want to assure what exists does continue to work well.

@mbyio
Copy link

mbyio commented May 10, 2018

@mattrobenolt thanks for taking the time to respond and for clarifying. I'm sure it's super hard to maintain clients for so many languages/platforms.

@kamilogorek
Copy link
Contributor

As for unaddressed PRs and issues, this is really hard for us right now. At the moment, we don't have a dedicated person on our team for raven-go.

I'll try my best to change this though :)
And as the first step (well, second after applying all code tooling suggestions) I'm triaging all the issue and cleaning up our GH issues/PRs. Thus let me close this one and feel free to open new one if there are some specific questions. Cheers!

# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants