Maple release - Testing, fixes contributions & upgrade

Yep, that’s definitely an option and something we’ve done before.

I’m not sure about that. The risk of work not getting completed on time and/or up to standard seems higher in this scenario than when giving upgrade work to newcomers that already completed their trial project successfully. If we use it sparingly, the approach may work, though :thinking:

Yes, these types of epics would be a good source of work for newcomers :tada: We’d just have to find/agree on a way to deal with sustainability implications. (The DevOps epics are usually on non-billable cell accounts, so if newcomers take longer to complete tasks than core team members would – which is not uncommon and understandable – this will impact cell sustainability negatively.)


:+1:

We have an epic (SE-4957) but no owner yet.

In terms of capacity, Serenity could keep this epic or take the blocking FAL-2081, but not both. (This is after incorporating the capacity updates from Campus.)

Since Bebop has the most context on Grove-related epics at the moment it would make sense to see if we can find a way to move FAL-2081 to Bebop. As far as I’m aware, one potential option would be for @giovannicimolin to take it on (cf. this comment).

CC @jill @farhaan

2 Likes