What still needs doing to release a 1.0 version?

[rkent]

          The good news for release version is that I am virtually at the end of my backlog of unreleased changes, so I expect that the pace of change will slow dramatically. It will be reasonable soon to do a 1.0 release of rosdoc2, and try to maintain a version numbering with breaking/feature/bug changes distinctions. Maybe we need an issue to discuss if anything more is needed for a 1.0 release.

The next phase of documentation improvement will primarily focus on helping and encouraging package authors to make their packages compatible with rosdoc2. The needed hooks for that are either already landed, or will be soon.

Originally posted by @rkent in #177 (comment)

[rkent]

I just submitted #178 which I believe is the last patch I have in my backlog of work on rosdoc2 that changes code. There is one remaining patch, and that is comprehensive documentation of the various options to use and configure rosdoc2.

After that, I think we should roll the rev to 1.0.0 and do another pip release. Any thoughts on that?