Planning ahead

[Ralph Castain]

Hi folks

I often receive bug reports and feature requests via email, which is fine. Many of them are simply notes I made while working on some other issue when I see some unrelated problem, or a question gets asked along the way that would spin off into another effort.

I’ve kept those in my notes for quite some time, dusting something off when I hit an appropriate point or have some free time. However, as things continue to wind down, I’m finding it a little harder to track where I am on a given effort, which branch in my repo fork holds the current state of the work, etc. We also have to face the inevitable where others may need to step up to finish and/or address things.

So I’m going to be transitioning the list over to filed issues, noting which repo fork branch is involved and something about the status of the work. History would say it is unlikely someone will pick these up, but if nothing else the community can see where the holes lie in case you encounter the problem in your own work.

Thus, if you see issues being filed with unusual text in them - this is why.
Ralph