This is an update to the thoughts I posted above. Something of a reversal.
As I stated previously, the main problem is that Serenity will not have the capacity to handle this on its own. It wouldn’t have the required sustainability, either, if it weren’t for the fact the epic is accelerated.
However, and this is what changed since my last post here, this sudden lack of capacity has had a large impact on my own sprints. I was already vying to reduce stress and improve efficiency by looking for something to focus on - and things have gone exactly in the opposite direction, unfortunately.
So, to keep it brief, I’m now looking for somebody to replace me as epic owner on SE-1834. (I’ll also be closing/relinquishing any planned or ongoing Ocim tasks, and will be dropping the devops specialist role, but that is for another thread.) I’ll continue as build-test-release chair, but only as a communication facilitator, so I’ll need whoever owns the epic to help me find assignees until Lilac is out. After Lilac, I’ll be opting out of release work entirely, and I suggest whoever takes this epic on should probably start attending the meetings.
Pinging @jill specifically: interested in taking it all on? 