Yes, those should already be set up, but let me know if I missed
anything (note that the "release" version of the manual still lives on zeek.org as there's not yet any release that can be build on RTD).
Not sure how worth it -- feel a bit odd/unmotivated preparing a
pure-cosmetic feature for a patch release which I usually think more
strictly in the Semantic Versioning sense as being bug fixes only, not
new features. Maybe a good segue to a separate discussion on
improving release/version planning so there's more appropriate and
frequent times to release smallish features like this?
Both release and master versions are on RTD (docs.zeek.org) now and
build from a new zeek-docs repo on GitHub.
The 2.6.1 version was manually imported with a few tweaks to get it
working, so don't think we have to consider backporting anything into
a 2.6.x -- probably those won't change the generated docs anyway so we
can get away with just bumping a new git tag.