Now that your V3F branch is released, we have a strong reason to release soon. To-do:

1. All the regular pre-release process stuff, especially squishing the high-priority bugs.

2. One of us should post a call for testing to the Google Group.

3. There remain references to "mkos8" that need to change to "os8-run".

4. Mark Pizzolato's bugged me a few times about re-testing some changes he's made to the SIMH timing core that affect the PDP-8 simulator's startup behavior. It's time to stop procrastinating on that, merge the latest SIMH, and report my findings.

5. Once we're happy with the new V3D media, they should replace the ones we're currently offering on the home page.

   (Should the V3F tapes join them, or do we wait for the V3F-on-RK05 project to complete first?)

I'd like to get this out before Christmas. Yes, Christmas this year. 😉

I've done a first pass on the ChangeLog. Please give it a read and touch it up as needed, Bill.

Are you the project's new maintainer? I think I might be responsible for more individual items in this release, but you're almost certainly responsible for more new and changed lines of code.

I ask because while writing new ChangeLog entries, my normal rule is "Everything not attributed to someone else was done by me," and this release is nearing the 50/50 point on that basis. If it passes that point, I'll want to change the rule.

Assuming my level of contribution stays flat or decreases, do you think the next release will be even more Bill and less Warren?

Forecasting is difficult, especially about the future.

Let's continue to talk about who is maintainer. I'm not yet comfortable taking on that mantle, but if I start making more massive changes throughout the system, then perhaps.