New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Redo README and add current status note #3750
Conversation
We no longer support Socorro and we're making big changes. Seems prudent to let users know the status and what the last good commit was.
@lonnen Is the text here clear enough? My concern is that I'm going to go delete all the collector code and given that users continue to use Socorro and ask for support, I don't think we've been super clear about how we're not supporting Socorro anymore and how we're making backwards-incompatible changes. So this text makes that clearer and gives them a sha for the last good commit (for some definition of "last good commit"). |
README.rst
Outdated
This is a very Mozilla-specific product. We do not currently have the capacity | ||
to support external users. If you are looking to use Socorro for your product, | ||
maybe you want to consider alternatives like `electron/mini-breakpad-server | ||
<https://github.com/electron/mini-breakpad-server>`_. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's list https://github.com/wk8/sentry_breakpad as an alternative also
README.rst
Outdated
Socorro | ||
======= | ||
|
||
Socorro is a set of services for collecting, processing, and displaying crash |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
consider adding a word or two to emphasize Mozilla-specific
README.rst
Outdated
|
||
Current deployment status: https://whatsdeployed.io/s-7M7 | ||
|
||
Infrastructure (AWS) code: https://github.com/mozilla/socorro-infra |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we note that this repo is similarly deprecated?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have no idea if it is or not. I thought it was Mozilla-centric and there was no expectation that it was supported in any way.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll add a note about how this is Mozilla-centric and not supported, too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rather than do a date-base series of updates as we pull components, consider anointing a tag as the last holistic release of the system. |
I'll switch it to a tag--that's a good idea. I was thinking "this is the last known good one" after which we have carte blanche to make any changes we want. I wasn't planning on doing further status updates. |
@lonnen ^^^ Does that look good? |
I think I addressed all of @lonnen's comments and that this is fine. If not, we can do another PR. |
Belated r+
…On Fri, May 5, 2017 at 10:55 AM Will Kahn-Greene ***@***.***> wrote:
Merged #3750 <#3750>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3750 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AABT2_clR8whmuE96qYSkCN-uh9cgJJkks5r22KTgaJpZM4NPyw6>
.
|
We no longer support Socorro and we're making big changes. Seems prudent to let
users know the status and what the last good commit was.