evaluate
then
integrate
evaluate
then
integrate
evaluate
then
integrate
:P
I mean, obvious first step is finding the britney code. I should point out that the promotion jobs (install checks) are largely what britney does. Britney AFAIK applies some policies (e.g. no new bugs?) then attempts the installation of the new candidate packages and then moves the passing packages over. i.e. where our current tech is an all or nothing deal, britney would do atomic migration (e.g. kamoso is fucked but plasma is not, plasma would still be able to get into user). Whether that is useful and makes sense for our use cases is where the evaluation comes in.
needs more research to check out what this is and what it does and if it's useful compared to our current stuff