Re: b4 review surfacing updated serieses

Konstantin Ryabitsev <[email protected]> Mon, 27 Jul 2026 11:37:59 -0400
Newsgroups org.kernel.linux.tools
Message-ID <20260727-innocent-zippy-sambar-51cfe4@meerkat>
On Thu, Jul 23, 2026 at 01:38:38PM +0100, Mark Brown wrote:
> One issue I have frequently with the UI for b4 is that it's not great at
> surfacing serieses which have new versions.  There's nothing in the list
> of serieses that says that a series has a new version, they stay sorted
> in the list with whatever date they arrived and you can't see that a new
> version is there until you actually highlight the series.
> 
> It also doesn't seem to reliably move things out of "waiting for new
> version" when there is a new version.

I've reworked the upgrade flow on a branch (feature/has-newer-first-class)
to cover both the waiting-upgrade awkwardness and the stuck-partial case.
Please give it a whirl -- it should be safe to try/back out as it doesn't
change the db schema. I don't have nearly as many series being reviewed as you
do, so I can't fully test it beyond what's in the test framework.

Specific changes:

Upgrade is now gated purely on a newer version existing, not on the series
state, so you can upgrade straight from waiting -- it archives the old branch
and drops you back into reviewing. A series with a new version also gets a
dedicated "up-arrow" marker and pops back up into the active list instead of
sitting at the bottom. There's now also a special "up:" filter for 'l' to show
just the series for which an upgrade exists. I dropped the old implicit
auto-upgrade-on-update while I was at it -- upgrading is now always something
you trigger, so hopefully there are fewer surprises or stale states.

Same change unblocks the partial case: [u]pgrade should no longer refuse
partially-applied series. The partial label itself can still linger after a
revert -- I didn't auto-clear it, since a revert leaves the commit in history
and guessing is worse than a stale label. Easy to add an explicit "reset
coverage" action if it's actually annoying.

I was hoping to get 0.16 out, but these look like real quality of life issues,
so it's best to get them working better before we invite others to try the
review features.

Thanks!

-K