Enable any Sourcegraph customer or user to trial or run (in production) Sourcegraph in a way that is compatible with their environment, supports their level of technical expertise, and allows them to easily access the value that our product provides. Make it as easy as possible to access this value, and to maintain it going forwards by easily staying up to date with Sourcegraph’s latest developments.
- Nelson Araujo, Interim Releases Lead (and Head of Infrastructure)
For more detailed information on the Release team members, check out our README page which expands on our profile.
Feel free to direct simple questions to us in #discuss-release-ship in Slack. As a rule of thumb, anything that is not documented in our handbook or docs usually indicates it is not a simple question (e.g. feature requests) and should follow our support request guidelines below.
- This channel is regularly checked and well-monitored
- So please do NOT directly message or CC an engineer—this is to try and protect their focus
- Instead, if it’s urgent, please mention
@release-teamin the channel and we’ll ensure it gets the best response
Support requests related to our areas of ownership should follow this process:
- Make sure there is an issue—if there’s not, please create one and include:
- A short description of the ask
- A more detailed explanation of the background, the context and the challenge that needs solving
- Any guidance related to the impact this is having
- Any extra information that could help us solve or prioritize this
- Ensure lable
team/releaseis added to the issue
- Ensure that the issue is added to the ”Release” board in GitHub
- Anything without a status is checked and triaged weekly - so this is enough for feature requests or less urgent issues
- If you think this needs eyes 👀 sooner
We inherit Sourcegraph’s engineering principles and practices.