Release planning

[sde1000]

Hi everyone!

You may have noticed that there are several new pull requests from @markus-becker-tridonic-com in the queue. I've had a look at them, and I am planning to merge them after I've tested them as well as I'm able to.

I'm going to take this opportunity to make some other changes that I have been thinking about for some time. I've never been happy with the drivers being in the library — we don't have an API that works for everyone, for example — and I've considered moving them to examples/ in the past. (See #69 and #149.)

I'm not going to do that. Instead I plan to split the project in two, creating a new project for drivers and leaving python-dali as a "sans-io" style interface to DALI.

I think this has at least the following benefits:

• python-dali becomes easier to test and maintain. It's there to implement and document the standards, and nothing else.
• It's made clearer that the drivers are not an "official" part of python-dali, and that if they don't work for you (you prefer threaded over asyncio, for example, or want the API to be different, or want to run on an OS with different ways of accessing hardware) then you can just write or find other drivers

Proposed plan

I suspect that many people who depend on python-dali have pinned major version '0'. So to avoid breaking things for them:

1. I plan to merge Add GitHub Actions workflow to publish to PyPI on tag #154 and use it to make a release 0.12 containing the current state of the project.
2. I'll merge the remaining pull requests except Typed #160 and make a release 0.13. (Typed #160 is a bit more global than all the other pull requests.)
3. I'll merge Typed #160 and then split the project. I'll remove drivers from python-dali and make a release 1.0, and in the new "drivers" project I'll replace the python-dali code with a dependency on python-dali, and make an initial release.

I hope I'll get a chance to do this in the next week or so. But before I do, are there any comments?