Conversation
|
Notifying subscribers in CODENOTIFY files for diff 5416f60...dce03e6.
|
| ### Repo config Experience (such as Repo syncing status) | ||
|
|
||
| Configuring code host connections and permissions syncing is a core prat of the admin experience, and historically, it has been painful to do. With Sourcegraph 4.0, we have introduced more than X quality of life improvements to help admins understand the current state of repository and permissions syncing. |
There was a problem hiding this comment.
| ### Repo config Experience (such as Repo syncing status) | |
| Configuring code host connections and permissions syncing is a core prat of the admin experience, and historically, it has been painful to do. With Sourcegraph 4.0, we have introduced more than X quality of life improvements to help admins understand the current state of repository and permissions syncing. | |
| ### Improved Repository Configuration experience | |
| Configuring code host connections and permissions syncing is a key component of admin experience and it has historically been a poor customer experience. With Sourcegraph 4.0, we have introduced more than X quality of life improvements to help admins better understand the current state of repository and permissions syncing. |
|
|
||
| With 3.42, we introduced an all-new admin analytics including. Now with 4.0, we're significantly improving on the initial release. 4.0 includes dozens of updates including pages for all Sourcegraph features, annual projections for dev-time-saved, data exports, individual user usage table, and much more. | ||
|
|
||
| ### 1-click log export |
There was a problem hiding this comment.
| ### 1-click log export | |
| ### Export Sourcegraph logs with 1 click |
sqs
force-pushed
the
sourcegraph-4.0-release-post
branch
from
a4a1b78 to
6ec3c03
Compare
| changelogItems: | ||
| --- | ||
|
|
||
| > NOTE: This post is very WIP. To be edited and tightened up a lot. |
There was a problem hiding this comment.
TODO - feedback from @abschu at https://docs.google.com/document/d/1EAXfMBidVX1WJERdtnU8x-urrjpnc-80-PoOzeQPNpw/edit
| Search is now more intelligent by defaul and automtically generates and runs alternative queries when your initial query doesn't have many results. This can be disabled so you still get only literal or structural matches when you need to, but in many cases the new smarter search is likely to be better. This will especially benefit new users of Sourcegraph who don't yet know the query syntax. The default query syntax is also simplified, allowing you to combine literal search terms and regular expressions with `/`'s like so: `authentication /^my|regex$/`. | ||
|
|
||
| ### Simplified UI | ||
| We've made a number of small usabilty improvements to simplify the search UI and make Sourcegraph feel less complex. |
There was a problem hiding this comment.
| We've made a number of small usabilty improvements to simplify the search UI and make Sourcegraph feel less complex. | |
| We've made a number of usability improvements to simplify the search UI and make Sourcegraph feel more concise and easier to use. |
Thinking that this is a bunch of small changes that make a big impact as a whole, so we shouldn't undercut it. I'm also suggesting phrasing it so that instead of "perceived bad" → "less bad," it's solely "better!"
iskyOS
changed the title
|
|
||
| `TODO(sqs): The section headers with emojis are what I think we should use, but the wording of the bullet points within are WIP` | ||
|
|
||
| ##### 🌅 Code intelligence: more useful, more times daily for every dev |
There was a problem hiding this comment.
@sqs @iskyOS - I really like the framing of finding/getting answers and information about your code vs simply finding things in your code. This comes through in both of your docs (Alex, SQS), but isn't apparent in this headline. I think things like precise code nav + auto-indexing, simple UI, smarter code search, and high-level aggregations all support answering questions/learning about your code.
Here are a few alts:
- Answer questions about your codebase with code intelligence: more useful, more times daily for every dev
- Understand your code with code with code intelligence: more useful, more times daily for every dev
- Get answers with code intelligence: more useful, more times daily for every dev
- Understand with code intelligence: more useful, more times daily for every dev
There was a problem hiding this comment.
@abschu I agree, I think this headline could do a better job of summing up the value of the section (and in this case, code intelligence won't be well defined by our audience yet)
I think I like this one most:
"Get answers with code intelligence: more useful, more times daily for every dev"
| - High-level aggregations of search results | ||
| - Precise code navigation for 9 languages (adding Ruby and Rust) with auto-indexing | ||
|
|
||
| ##### 🏗️ High-leverage ways to improve your entire codebase |
There was a problem hiding this comment.
I love the framing of "improve your entire codebase."
|
|
||
| ##### ☁️ Enterprise Cloud dedicated(/managed?) instances | ||
|
|
||
| - [Secure, easy, and scalable Sourcegraph Cloud dedicated(/managed?) instances for the enterprise](/blog/enterprise-cloud) |
There was a problem hiding this comment.
@abschu Totally agree; I think it'll also make it fit in with the other headlines more.
"Cloud instances: secure, easy, and scalable"
|
|
||
| But as developers of software, we all feel the pain of code complexity: the struggle to understand big codebases, not being able to get in flow, encountering tech debt that turns a tiny fix into a multi-day ordeal, all the wasted time, etc. | ||
|
|
||
| Code search is helpful in tackling complexity, but it's not enough. Code search is for finding things *in* code (matching lines in files). What helps you find things *about* code? Let's call it a code intelligence platform. Compared to code search, it's more helpful, more times per day. This is like how Google went from helping you find things *on* the web (matching web pages), to helping you find things *from* the web (information and answers). Here are some examples `TODO: make it clear which these are available and which are future directions`: |
There was a problem hiding this comment.
Comment from @felixfbecker (in the previous draft gdoc):
This alone doesn't really justify the name "platform" to me (making it appear to me as a dev and unfamiliar reader as a marketing buzzword without substance). A platform is something that you can build other things on top of. I think if we want to show and explain that we're becoming a code intelligence platform, we need to talk about why we're sunsetting our extension API (they didn't deliver on the platform promise, because they were UI only) and what our future vision is that is soon to come over the 4.x releases (metadata, ownership, ...).
Maybe we can even talk about some things that are shipped in 4.0 that show that direction/vision. E.g. is the repo metadata by the search team going to be ready to be talked about? That's simple, but it clearly shows the difference between UI-only extensions and persisted data that becomes available to search queries, to the GraphQL API, code monitors, to search aggregations (also shipping in 4.0), ...
That paints the picture of an actual "platform" to me (you can imagine how you could eventually build entire tools like coverage tracking on top of Sourcegraph by uploading the data into Sourcegraph, using it in queries, dashboards, code monitors, ...)
There was a problem hiding this comment.
I think there's an opportunity here to articulate that this is a platform because we are building new products and use cases on top of the core search technology.
There are different ideas around of what defines a "platform", but for us, all of our product suite is built with a hard dependency on Search technology - which is a big part of it being a platform for us.
|
|
||
| This feature requires admins to set up executors (much like CI agents), which Sourcegraph will use to offload expensive tasks. Executors can also be used to run [Code Intelligence auto-indexing](#TODO-link-to-section-or-docs). If you're on cloud, one or more executors are available by default on your instance. | ||
|
|
||
| ### See high-level aggregations of your search results set, to quickly answer questions about usage and structure |
There was a problem hiding this comment.
Until we have images for the post, you (internal teammates) can see the full scope of this feature and rough mocks in the source of truth spec RFC 727.
|
|
||
| ##### 🏗️ High-leverage ways to improve your entire codebase | ||
|
|
||
| - Run batch changes server side |
There was a problem hiding this comment.
This resonates with me, but I wonder if it would be more effective to phrase it in a way that focuses less on the product and more on what it makes possible. (Like, what are batch changes and why do I care if they are run on the server side?) But I'm having a hard time condensing it from the paragraph in my head into a punchy bullet point.
@malomarrec Any ideas here?
There was a problem hiding this comment.
Oh, duh, you totally say the same thing later down the page 🤦🏻
There was a problem hiding this comment.
Yeah I think it boils down to "who's the target audience", @abschu ?
If we are trying to exhibit the delta (what you can do now you couldn't before),keep as is. Alternatively, ignore server-side, and re-introduce Batch Changes from scratch.
In which case, the bullet point could just be "Apply and track automated code changes across your codebase. Now supports very large scales thanks to running server-side (link)"
There was a problem hiding this comment.
@malomarrec @chrispine - we should focus on what's new, but also use this as an opportunity to explain what Batch Changes is.
| changelogItems: | ||
| --- | ||
|
|
||
| > NOTE: This post is very WIP. |
There was a problem hiding this comment.
@sqs here's the outline of @beyang's blog we discussed late last week: https://docs.google.com/document/d/1dZxT9iiUfnNUw6EZHbhJS0uxdfV53qNV4EMAfjlL6PM/edit#heading=h.ndoqaqxyl2nz
|
|
||
| - [Secure, easy, and scalable Sourcegraph Cloud dedicated(/managed?) instances for the enterprise](/blog/enterprise-cloud) | ||
|
|
||
| ##### 💖 For admins |
There was a problem hiding this comment.
@iskyOS @lcolston08 - are we going to mention multi-version upgrades in the release post?
There was a problem hiding this comment.
@abschu I think we should. I think multi-version upgrades is one of the bigger items in 4.0; it'll allow customers on old versions to finally realize all the value that's been added over the last 6 months, year, etc
There was a problem hiding this comment.
Same. It should be listed as a key feature under the Love for admins theme. So this would mean higher up in our features under that theme.
|
I clarified that server-side is in beta |
@lcolston08 just bringing this to your attention |
|
Thanks for bringing that to my attention @malomarrec |
| changelogItems: | ||
| --- | ||
|
|
||
| # Sourcegraph 4.0 |
There was a problem hiding this comment.
@lcolston08 @iskyOS is it possible for marketing to make the PR to first input the template as you would like it? It seems like this is just a format change, rather than an information change. (We all have the information on our features in this post already.)
There's a chance we'll end up with some odd formatting inconsistencies if we all patchwork various aspects of this template and it'll probably be much faster to have 1 person take the information already in this blog post rather than have to chase down 9 other individuals to just make the same reformatting change (if I understand that's what this request is).
|
|
||
| Code search isn't enough to answer these kinds of questions, because code search doesn't know all the other necessary information about code. Code search just helps you find matching lines in code. TODO sqs - (thats why we are calling it ...) | ||
|
|
||
| We added [Code Insights](https://docs.sourcegraph.com/code_insights) to let devs track trends over time, [Batch Changes](https://docs.sourcegraph.com/batch_changes) to let devs make large-scale code changes across many repositories, and more. These crucial primitives helped, but we still needed to teach Sourcegraph much more about code and its associated metadata. |
There was a problem hiding this comment.
| We added [Code Insights](https://docs.sourcegraph.com/code_insights) to let devs track trends over time, [Batch Changes](https://docs.sourcegraph.com/batch_changes) to let devs make large-scale code changes across many repositories, and more. These crucial primitives helped, but we still needed to teach Sourcegraph much more about code and its associated metadata. | |
| Beyond search, we've already added [Code Insights](https://docs.sourcegraph.com/code_insights) to let devs track trends over time, [Batch Changes](https://docs.sourcegraph.com/batch_changes) to let devs make large-scale code changes across many repositories, and more. These crucial primitives helped, but we still needed to teach Sourcegraph much more about code and its associated metadata. |
|
|
||
| And that brings us to Sourcegraph 4.0. ... TODO ... We're making the same kind of leap, from a code search tool to a code intelligence platform. If we do our job well, Sourcegraph's code intelligence platform will free up so much time and brainpower for devs everywhere so that software progress can continue. | ||
|
|
||
| We've spent 9 years building the underlying foundation of code search to be fast, secure, and scalable across ~10^11 lines of code for the world's most demanding software teams, and now we're hard at work making Sourcegraph even smarter. [Sourcegraph 4.0](/blog/enterprise-cloud) is the first step toward Sourcegraph becoming a code intelligence platform, with smart search aggregations to quickly answer questions about usage patterns. |
There was a problem hiding this comment.
| We've spent 9 years building the underlying foundation of code search to be fast, secure, and scalable across ~10^11 lines of code for the world's most demanding software teams, and now we're hard at work making Sourcegraph even smarter. [Sourcegraph 4.0](/blog/enterprise-cloud) is the first step toward Sourcegraph becoming a code intelligence platform, with smart search aggregations to quickly answer questions about usage patterns. | |
| We've spent 9 years building the underlying foundation of code search to be fast, secure, and scalable across ~10^11 lines of code for the world's most demanding software teams, and now we're hard at work making Sourcegraph even smarter. | |
| [Sourcegraph 4.0](/blog/release/4.0) is the first step toward Sourcegraph becoming a code intelligence platform, and is available today. Sourcegraph 4.0 includes over a dozen updates and new features that make answering questions *about* code as easy as searching for matching lines *in* code. | |
| Today, we're also launching [Sourcegraph Cloud:](/blog/enterprise-cloud) secure, scalable, dedicated Sourcegraph instances on the cloud. Sourcegraph Cloud is the best way to start using Sourcegraph on your organization's code. [Sign up now](https://signup.sourcegraph.com/). | |
Co-authored-by: Felix Becker <felix.b@outlook.com>
…/about into sourcegraph-4.0-release-post
Auto-indexing docs link
abschu
left a comment
abschu
left a comment
There was a problem hiding this comment.
@lcolston08 - updated the em dashes for multi-version upgrades.
| <Badge link="https://docs.sourcegraph.com/admin/updates#multi-version-upgrades" text="Admin" color="violet" size="small" /> | ||
|
|
||
| #### Upgrade directly to Sourcegraph 4.0 from earlier versions of Sourcegraph | ||
| We know that upgrading Sourcegraph can be a time-intensive process, especially if you fall a few versions behind. Sourcegraph 4.0 supports [multi-version upgrades](https://docs.sourcegraph.com/admin/updates#multi-version-upgrade) so you can upgrade to 4.0 – and any future version – directly from version 3.20 or higher. |
There was a problem hiding this comment.
| We know that upgrading Sourcegraph can be a time-intensive process, especially if you fall a few versions behind. Sourcegraph 4.0 supports [multi-version upgrades](https://docs.sourcegraph.com/admin/updates#multi-version-upgrade) so you can upgrade to 4.0 – and any future version – directly from version 3.20 or higher. | |
| We know that upgrading Sourcegraph can be a time-intensive process, especially if you fall a few versions behind. Sourcegraph 4.0 supports [multi-version upgrades](https://docs.sourcegraph.com/admin/updates#multi-version-upgrades) so you can upgrade to 4.0—and any future version—directly from version 3.20 or higher. |
Multi-version upgrades section.
abschu
left a comment
abschu
left a comment
There was a problem hiding this comment.
@lcolston08 - a few final updates - thank you!
| #### A faster, simpler search experience | ||
| We streamlined and simplified the search user interface to make the platform more intuitive. The search homepage, for customer instances of Sourcegraph, now has contextual tips and recommendations using real data from your instance, including repository names, file names, and authors. This information makes it easier and faster than ever to run a successful search query. | ||
|
|
||
| [Search results](/code-search) are now front and center with the improved interface. The search sidebar has moved to the right side of the screen, matches in file and respository names are now highlighted, and we eliminated several non-essential elements to ensure the information you need is easy to access. Filters make it effortless for you to answer questions about your code, and the sidebar can be collapsed altogether to reduce noise. |
There was a problem hiding this comment.
@lcolston08 - this should either link to the docs or we should remove the link. This is more about search results vs our code search product.
|
|
||
| Remember how Google went from helping you find things *on* the web (matching web pages) to helping you learn things *from* the web (information and answers) by connecting data like news, videos, and maps back to web search? Today, you go to Google to answer complex questions and learn things, not to find things. | ||
|
|
||
| We're making the same kind of leap. We've spent 9 years building the underlying foundation of code search to be fast, secure, and scalable across ~10^11 lines of code for the world's most demanding software teams, and now we're hard at work making Sourcegraph even smarter. [Sourcegraph 4.0](/blog/sourcegraph-4.0) is the first step toward Sourcegraph becoming a code intelligence platform. No newline at end of file |
There was a problem hiding this comment.
| We're making the same kind of leap. We've spent 9 years building the underlying foundation of code search to be fast, secure, and scalable across ~10^11 lines of code for the world's most demanding software teams, and now we're hard at work making Sourcegraph even smarter. [Sourcegraph 4.0](/blog/sourcegraph-4.0) is the first step toward Sourcegraph becoming a code intelligence platform. | |
| We're making the same kind of leap. We've spent 9 years building the underlying foundation of code search to be fast, secure, and scalable across ~10^11 lines of code for the world's most demanding software teams, and now we're hard at work making Sourcegraph even smarter. [Sourcegraph 4.0](/blog/release/4.0) is the first step toward Sourcegraph becoming a code intelligence platform. |
Co-authored-by: abschu <andy@sourcegraph.com>
Co-authored-by: abschu <andy@sourcegraph.com>
Co-authored-by: abschu <andy@sourcegraph.com>
Co-authored-by: Felix Becker <felix.b@outlook.com>
Co-authored-by: Felix Becker <felix.b@outlook.com>
removed code search hyperlink
| description: Announcing Sourcegraph 4.0. The latest release includes over a dozen updates and new features, and it is the first step toward Sourcegraph becoming a code intelligence platform. | ||
| tags: [blog, release] | ||
| slug: "release/4.0" | ||
| published: true |
There was a problem hiding this comment.
@iskyOS IMO we should add authors: whoever primarily wrote the main part, and then the authors of each section. even if it's a lot of authors. if this is too complex to have a lot of authors, feel free to disregard.
There was a problem hiding this comment.
I like this idea @sqs! I don't know if our blog rendering will support that # of authors, but we can test it. I'd also like @lcolston08 to help figure out who those authors should be (and she was the main author).
My recommendation for now is to go forward with the blog as-is, and in the morning we can test the limits on # authors (and Lori can help us figure out who those authors are). We can also merge that as a new PR shortly after this goes live
20 participants
Creating the Sourcegraph 4.0 Release Post blog. This blog post should be used to stage and track updates to the 4.0 release as they are being worked on and committed to the build.
WIP links:
Live Previews: