-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Core Services: 3.10 tracking issue #6031
Comments
@keegancsmith: Are we going to organize a planning meeting soonish? |
yes. @sourcegraph/core-services please update the issue description with what you might want to work on. Defer on the side of adding too much, then we can trim it down in our planning meeting. Please do so by EOD Wednesday (@kzh @unknwon). I assume automation work will be tracked separately. Edit: Each item you add to the tracking issue, please link to another issue with some details of what you want to do for that issue in 3.10. (ie the issue should be closeable in 3.10, even if the broader issue isn't complete). |
Yes. |
Please invite me to the planning meeting. |
Note: Ryan#2 will join core services during this iteration, Oct 30th IIRC. #2587: Expose full repository languages/file types inventory via GraphQL is what we proposed for his first project during our roadmap meeting. |
I think my proposed work on structural search falls under core services, so added it as well. |
@rvantonder Welcome to the core services 😁 |
I've updated the description taking into account all the edits done. Please give a 👍 if it looks good to you, otherwise comment / edit then do a thumbs up. @kzh @unknwon can you create tracking issues for the implementation work on the respective RFCs. The only thing that is missing that seems like it may make sense to do in 3.10 is RFC 33: Usage-based billing. Thoughts? Please propose anything we need to discuss that is currently missing from the description. As it stands this seems pretty well shaped, so I don't think we need to do a full meeting on it. We can also continue some discussion async on this issue. If all goes well I am thinking we can discuss it in our next sync (Tuesday). @tsenart I know you asked about a planning meeting, what do you think about doing things more async + a shorter meeting as part of our weekly sync? |
Sounds good to me. |
Added.
Asked @dadlerj last Friday, and I believe he thinks it is not a high priority thing to do at the moment. But we could still plan it since we're going to need this anyway in the long term. |
Quinn added https://github.com/sourcegraph/sourcegraph/issues/5519#issuecomment-538321132 to project roadmap as Diff search across 25+ repositories - TODO prioritize at next sync with a comment. |
Added to the next Core Services sync agenda. |
W42 Plan [2019-10-21]Working days left to vacation: 9 |
W43 Plan [2019-10-28]Working days left to vacation: 5 Must ship: Fully tested, documented and ready for release version of horizontal search. Otherwise I plan on writing an RFC this week (undecided on what, got a few ideas). Managed to hit my plan for last week and horizontal search v0 is in master \o/. |
Shipped! Please read the important notes at https://github.com/sourcegraph/sourcegraph/issues/5725#issuecomment-548730923
Didn't manage to get around to this. Holiday time, see you all in two weeks. |
Dear all, This is your release captain speaking. 🚂🚂🚂 Branch cut for the 3.10 release is scheduled for tomorrow. Is this issue / PR going to make it in time? Please change the milestone accordingly. Thank you |
Structural Search Structural Search MVP is merged. I:
Structural search is activated by typing Some parts of integrating with search took longer than expected and I didn't get to RFC 48 part 2 (strictly a performance increase, no change in functionality), and triage it for next release. |
Theme: What will break with 80k repositories across multiple code hosts?
Q4 Vision Statement: Sourcegraph operations are fast (e.g. search), instances scale to 80k repositories, private code is secure and respects ACLs for every authorization provider, and the product settings are easy to set up and understand for our largest customers.
Housekeeping
Required
@ryanslade we have assigned a task for you. Once you have joined and onboarded a bit we can change the task, this is a good initial task to try out but there may be something more appropriate. It is also under the "required" section. However, you will be onboarding so this can slip. We can also update this document with your real GitHub handle when appropriate :)Polish
These are smaller tasks which anyone can do. They are all stretch tasks, with the main tasks being first priority.
Note: If the task is assigned to someone already, you can do it (please ping the person first).
Single ctags docker image for both unindexed symbol svc and ZoektSingle ctags docker image #6080Rename Sourcegraph Go module to succinct nameUpdate module to sourcegraph.com #49823.9 tracking issue is #5710
The text was updated successfully, but these errors were encountered: