OK. I guess I can put this on a user branch for integration? (for what it's worth, combining business accounting with the Git branching has its downsides)

It would certainly be better to merge this after v14 is out (the tutorial won't be compatible with the 13 or 13.1).

DM-11077 and DM-11034 are related tickets that add additional tutorial steps. Should I treat those tickets the same way? Close for now and add them to the new review ticket?

For fear of them getting lost, I submitted some preliminary comments on the PR.

Thanks Lauren MacArthur!

Sorry for being slow on getting back to this.

OK. I guess I can put this on a user branch for integration?

(for what it's worth, combining business accounting with the Git branching has its downsides)

I think that's partially true, but you yourself raise another issue here: we don't want to merge to master until after the next release.

(Actually I'm not sure how that'll work in general — will we tag pipelines_lsst_io at the same time as everything else which makes up the release? And show the version corresponding to the most recent release, rather than master, by default?)

DM-11077 and DM-11034 are related tickets that add additional tutorial steps. Should I treat those tickets the same way? Close for now and add them to the new review ticket?

I think the same approach, but maybe making a separate "review" ticket for each one, rather than combining them all into one.

Thanks for your help with this!