Release planning

[BoboTiG]

As discussed in #469 comments, I would like to cut a minor release with all awesome changes that happened the past weeks. These are non-breaking changes with a potential huge impact on user code (in the good term).

So, after #469, do you need more stuff added to MSS before the release? I know @jholveck will add the Linux equivalence. Lets sync here with @halldorfannar also.

---

After the minor release, lets break some things (like in #470) and perhaps more to come.

[halldorfannar]

Sounds like a plan. Before we cut this minor release, we should give @jholveck an opportunity to add primary monitor support for Linux. As part of that work, we may also adjust the name field that we currently have and rename it to model (or model_name). We can then also introduce the Unique Identifier (uid) that Joel and I have been waxing poetic about.

As for the release after that one. We should discuss what breaking changes makes sense to do. One of them is captured in #470. But I believe Joel and I will run into more potentially breaking changes as we start using the more modern Linux/Windows APIs for screen capture. Now, my idea was to do this via new interfaces - so that the old path was still there for those who were content with that. I.e. we wouldn't force people forward. But again, I haven't dug into the details so it remains to be seen how realistic that plan of mine is.

[BoboTiG]

That makes sense. I am not in a hurry, and when you guys have more information about potential breaking changes required, we could discuss it here or in specific tickets.