Release Plan about etheos

[ethanmoffat]

Hey, sorry I missed this since I was on vacation.

1. I haven't been tracking changes beyond just committing to master. I mostly wanted to dump my changes from MSEOSERV in my personal account on top of this fork. The major changes are

• Add (optional) logging of packet data
• Add working NPC dialog
• Add support for SQL server database engine
• Update engineering system to be more robust / automated (including VS compilation)
  I don't know if any of this warrants a major/minor version increment, if we do "release" I'd call it 0.7.1. But I'm open to discussing this.

2. The bug tracker on eoserv.net is the authoritative source. I agree on use of GitHub issues. I would like to port over the bugs from eoserv.net, but there are a lot on there...

3. Agree on use of PRs. I think what we discussed via discord is that organization members could submit PRs to master directly from branches, while other users would need to fork and submit PRs that way.

4. I haven't considered "release" timing or what we want to include. I'd like to automate pipelines around this, so that PRs merged into master trigger a deploy of the software to different dev environments (maybe for different DB engines) so that we have multiple test beds. Then a "release" could involve deploying an "official" image to e.g. eoserv.moffat.io (my current test server).