<mapreri> if you are fine with people uploading the package directly to the archive we can work it out, i.e. I upload a -2 as soon at 0.26.2-1 is uploaded, but then your next upload done through whatever CI should contain it.
<alan_g> mapreri: that would work for me
<mapreri> I have no idea how bileto (or whatever kind of CI/landing system) you are using work
<mapreri> oh, great
<mapreri> so, what would be the timing for 0.26.2 to land? :)
<alan_g> mapreri: out of my hands, first QA need to approve and then someone needs to push to archive. But I'd guess the next day or two.
<mapreri> that works just fine
<mapreri> I'll arrange the -2 upload, will you please merge it in 0.26.3 in the meantime?
<alan_g> AFAIK 0.26.3 doesn't exist (and likely won't). But I'll take care of it in that contingency.
Resolved on #ubuntu-mir...
<mapreri> if you are fine with people uploading the package directly to the archive we can work it out, i.e. I upload a -2 as soon at 0.26.2-1 is uploaded, but then your next upload done through whatever CI should contain it.
<alan_g> mapreri: that would work for me
<mapreri> I have no idea how bileto (or whatever kind of CI/landing system) you are using work
<mapreri> oh, great
<mapreri> so, what would be the timing for 0.26.2 to land? :)
<alan_g> mapreri: out of my hands, first QA need to approve and then someone needs to push to archive. But I'd guess the next day or two.
<mapreri> that works just fine
<mapreri> I'll arrange the -2 upload, will you please merge it in 0.26.3 in the meantime?
<alan_g> AFAIK 0.26.3 doesn't exist (and likely won't). But I'll take care of it in that contingency.