Closed tsenart closed 4 years ago
@sourcegraph/core-services: This is a first pass at our 3.12 tracking issue. It's not final.
@keegancsmith and I have triaged customer issues today. Next week we'll do roadmap items and technical debt. If you have ideas for those, or for any customer issues we have missed, please comment in this issue.
Additionally, write up your availability in the appropriate section.
PS: We haven't pursued https://github.com/sourcegraph/sourcegraph/pull/7142 for preparing the tracking issue because our Sourcegraph extension that expands customer Hubspot links doesn't work in PR views.
Possible item to add (don't know if we plan to hit it this iteration, I will probably tackle parts of the language, if not the implementation):
(I don't know which customer.)
@sourcegraph/core-services: I previously included weekends in my availability. That was a mistake. If you have done the same, please change.
@ryanslade: Hope everything is going well with the newly extended family :-) I'm updating your availability above as per the Not Working calendar. I know you've been busy so I'm not sure it's entirely up-to-date. If so, let us know when you find a few moments.
@rvantonder: Added your suggestion to the items. Are there other things you want to be doing in 3.12 that are not in there yet? If so, please add.
We have reviewed the open debt
core services issues and have deemed none of them a high priority relative to customer issues and the still to be determined roadmap items.
Without the roadmap items that we're still going to add on Thursday, the current list of customer issues accounts for 25d of work which fits well within the 59d availability we have.
@kzh: Added "Integrate Bitbucket Server Plugin's permissions endpoints #7282 3d ๐ ๏ธ@kzh" to the tracking issue.
I have roughly blocked out the time that I'd like to allocate to tasks this iteration with time estimates, but it is not finalized. See PR description.
@rvantonder, @unknwon: Added each of your issues to the 3.12 milestone and to the Core Services 3.12 project.
@sourcegraph/core-services: The total estimated work accounts for 75d which goes beyond our availability. I propose we take these customer issues out of this iteration (and tackle them next one):
archived
/fork
"yes/no/only" values are confusing #7003 5d ๐ฉThis would bring the remaining estimated work to 53d which leaves us some slack. In any case, it'd be good to assess in the next retrospective how or if having slack has had a positive impact.
Please :+1: or :-1: the proposed changes.
repo-updater: Soft delete rows in the repo table #6859 1d ๐ ๏ธ
Spent some time hacking on this with @unknwon today. I fear this is more like 2 days work, we ran into a few issues making it non-trivial. IE 2 days due to needed research and experimentation.
I removed the three customer issues mentioned in https://github.com/sourcegraph/sourcegraph/issues/7190#issuecomment-567598405 from the list of work.
While everyone is on holiday this week...
I'm going to continue working on "RFC 40: GraphQL APIs #7298", and try to experiment more on repo soft-delete from where @keegancsmith and I left on last pair session.
Still need to catch up and sync with everyone, but this is my plan for this week as it stands. My main goal is to experiment with code host fingerprinting. This is to get an idea of what is possible w.r.t. minimizing the number of steps an admin needs to do to setup codehosts on Sourcegraph. See #7464 for a scoped issue for this work for this week.
Other issues I plan on tackling this week:
Before the winter break, I finished implementing the GraphQL API for Campaigns in draft-mode. See https://github.com/sourcegraph/sourcegraph/pull/7278
Since that went a lot faster than I estimated, I have time left in this iteration for other things. So I started working on "updating Campaigns", which is the the next highest prio item on our roadmap.
If you want some to get some more context and my thoughts on that item, read these two slack threads:
I started to work on this in this PR: https://github.com/sourcegraph/sourcegraph/pull/7328
My plan for this week is to
Last week, 1 working day
I worked on
Week 2020-01-06 to 2020-01-10
I will work on (and probably finish) these items this week:
a8n: Upsert ChangesetEvents from Bitbucket Server webhooks
#6726 this iteration.Integrate Bitbucket Server Plugin's permissions endpoints
#7282 on customer/dogfooding instances.Last week, 4 working days
I worked on
Week 2020-01-06 to 2020-01-10
I will work on:
My update for Week 1
Last week 2020-01-06 to 2020-01-10
This week 2020-01-13 to 2020-01-17
count
parameter for structural search (rework a PR in progress https://github.com/sourcegraph/sourcegraph/pull/7491)Last week I planned to spend time on code host fingerprinting #7464, but all the other tasks I ended up working on took up the full week. In particular I ended up tackling setting TLS/SSL setting for communications for all code hosts/git. That is currently in progress and should be complete before branch cut. Soft-deletes in the repo table also took up a considerable portion of time.
This week has 4 main parts to it:
@ryanslade: Are you doing this in time for branch cut?
My plan for this week is to
Update: Added https://github.com/sourcegraph/sourcegraph/issues/7356 to the top of the list.
My plan for this week is to
Last week, there was a lot progress towards #6726. The core functionality is complete.
Today, I'll do some housekeeping: releasing v1.2
of Bitbucket Server Sourcegraph plugin, documentation, automatically creating webhooks for BBS.
Last week, I finished up RFC 40: GraphQL APIs #7298 except regression test suite.
I removed item "RFC 40: Handle change of bind_id in site config #7301 0.5d" because (as I commented on the issue) it might not be the ideal solution the prospective customer wants, thus not worth working on it at this point.
I added "RFC 40: Grant permissions on user creation and email verification #7679" because it is a necessary step (missed back when I added iteration items) for the preview version of RFC 40.
Dear all,
This is your release captain speaking. ๐๐๐
Branch cut for the 3.12 release is scheduled for tomorrow.
Is this issue / PR going to make it in time? Please change the milestone accordingly. When in doubt, reach out!
Thank you
3.12 done. Continue on with 3.13 https://github.com/sourcegraph/sourcegraph/issues/7719
Context
Status: This tracking issue is finalized.
Availability (59d)
Period is the Dec 16th -> Jan 15th. Please put in the days you won't be working and the number of working days for the period. Merry Christmas and a happy New Year! :santa: :christmas_tree:
Total availability, excluding @mrnugget, @ryanslade (a8n) and @tsenart (management): 16 + 15 + 15 + 13 = 59d
Planned work
All planned customer issues, technical debt and roadmap items are meant to be finished in the iteration. If we don't finish all planned work, it is either due to unknown unkowns or our estimating accuracy. While we cannot work on the former, we can on the latter โ over time, we aim to estimate better.
Roadmap items may take more than an iteration to implement. As such please link to an issue which is scoped to this iteration. IE the issue should be closed at the end of the iteration.
All issues listed need to have a number of days estimate attached. When setting days, try and overestimate the time needed. Do not use a granularity less than half a day. The total amount of work assigned to you needs to be about 75% of your available days.
Items
Legend