Irfan Alibay

To be honest we need to rethink how we do verbosity completely with parallelism, iirc tqdm as used currently behaves badly. (there was an issue about this somewhere)

We could parse the BIOMT matrices if present and expose them, that should be easy enough.

I don't necessarily think we need a new topology attribute for this, it's should be a single matrix for the whole system. Probably the simplest thing here is to store...

Do we need to do anything here? As far as I'm aware all this means is that starting next release (i.e. 2.1.0) I'll just make a tag and/or feature branch...

We'll see how it plays out in practice, but yeah I was planning to do something similar-ish. 1. PR to tie off version numbers + changelog 2. Complete feature freeze...

After speaking with @lilyminium we'll need to make sure we have a release feature branch so that the userguide has somewhere to point to.

> Does the user guide point to a branch or to a commit? Anyway, branching out of the tagged commit shouldn't be an issue. I'll leave this to discussions with...

Just keeping this open for now, got a few documentation things to update still.

@lilyminium does anything need to be done re: useguide?

Is this something worth reviving for @BFedder's GSoC project?