Distribution: 2020.10.20 - Vibrant Beetle #14408
Comments
|
This week:
Next week:
|
|
This week:
Next week:
|
|
Last week Some handbook updates (deployments, prometheus), improvements to alert solutions documentation rendering. Made more improvements to releases: reduced timeline, date formatting, etc. Took a stab at continuous sourcegraph upgrade tests (https://github.com/sourcegraph/sourcegraph/pull/14974) and using campaigns in releases (https://github.com/sourcegraph/sourcegraph/pull/15032) This week Continue working on https://github.com/sourcegraph/sourcegraph/pull/14974 and land sourcegraph/about#1838 . Turns out the automerge for license updates isn't working out - gonna circle back to that and see if that's easy to fix: https://github.com/sourcegraph/sourcegraph/issues/14766#issuecomment-716486279 |
|
Last week I have cleanup unused AWS resources and reviewed a couple of RFCs (RFC-249, RFC 245) and PRs. I have also been working with CE on the support pipeline. This week Im working on https://github.com/sourcegraph/sourcegraph/issues/13627 porting the checks to blackbox-exporter and merging the improved deployment pipeline goal and planning the next sprint. |
|
Last Week A lot of focus and firefighting with the release. Getting this into the hands of capital one and helping them with a small hiccup due to not following the upgrade path. Closing out sourcegraph/sourcegraph#12340 and breaking that down into smaller issues for each failing component, however the infrastructure in place can now be used more generically for other tests This week Continue work on the failing regression/qa tests as well as help Robert and Dax with their efforts to test upgrades and k8s deployments. |
|
This week Pushed through as much hand-off as I can, mostly spent time documenting things and walking others through various processes. Up-to-date project board with where I am at here. Next week I expect to finish all hand-off tasks I have and close out that project before heading out to go on vacation for two weeks. Aiming to set myself up with as clean a slate as possible for when I return. I also hope to start work on my first high-impact, low-cost win by starting to investigate reducing the time it takes to loadd/display search results. |
|
This week: I task switched and spent most of my time on https://github.com/sourcegraph/customer/issues/74. After that, I then recorded and released released a rough draft of the Dhall demo video (https://github.com/sourcegraph/sourcegraph/issues/14646) for @sourcegraph/distribution to review in https://sourcegraph.slack.com/archives/CJX299FGE/p1604110703335500. Next week: I will respond to feedback on the rough draft Dhall video that I shared, and I aim to restart work on https://github.com/sourcegraph/sourcegraph/issues/13340 |
|
This week Finalized and landed campaigns in releases and "closing" a release. Performed some instance upgrades for $CUSTOMER, made some progress on sourcegraph/server upgrade tests, made handbook updates for releases and managed instances. Opened a PR cleaning up how versions are configured in the release tooling (sourcegraph/about#1880). Next week Plan issues for 11.03 work (release tooling + k8s.sgdev marketing). Try to wrap up issues kicked from this sprint to 11.03 (sourcegraph/server upgrade tests, automerge). |
|
This week Next Week |
|
Last week This week |
Plan
Support new and existing deployments
This is an ongoing expense, we anticipate this taking no more than 5d of work spread across the entire team.
Create a Dhall demo to gather customer feedback
We would like to create a demo that we can share with customers and gather feedback about our proposed solution.
Releases are created in a single day
We have a goal of reducing the time it takes to create releases, and this current several-day system has encouraged us to view releases as “baked” rather than “snapshots of the main branch”, leading to situations where main is broken and we have to retrospectively fix it or adding last minute features.
Availability
Period is from October 20th to November 2nd (10 working days). Please write the days you won't be working and the number of working days for the period.
Tracked issues
@bobheadxi: 7.00d
deploy-sourcegraph: mark automated PR failures as release-blockers(#14622) 0.50dqa: automated sourcegraph/server upgrade test(#13877) 3.00dset up automerge for third-party license updates(#14766) 0.50d 🎩Completed: 3.00d
#14925) 🐛#14911) 0.50d#14626) 0.50d 🐛#14971) 1.00d 🎩#14912) 0.50d#14998)#97) 0.50d 👩@davejrt
Completed
#11717)#122) 👩#115) 👩#13627) 🧶#12340)@daxmc99: 4.00d
Automate Kubernetes cluster QA tests(#13878) 4.00dCompleted
#14865)#11496)#14998)@efritz
@ggilmore: 5.00d
Create customer demo video for dhall direction(#14646) 5.00dci: build and pin tool apks in CI for release(#13297) 🧶Completed
#74) 👩@pecigonzalo: 1.00d
Completed: 1.00d
#14582) 1.00d#13627) 🧶@slimsag: 0.50d
sourcegraph/customer(#119) 👩Completed: 0.50d
#14864)#84) 👩#122) 👩#120) 👩#103) 👩#14998)#74) 👩#14875) 0.50d@uwedeportivo: 5.00d
Create customer demo video for dhall direction(#14646) 5.00dLegend
The text was updated successfully, but these errors were encountered: