I'm convinced that MD on Github supports tables as well. There is also helper bash script to automatically format tables. Let me check that and get back at you.casainho wrote: ↑Feb 01 2020 1:45pmI think those 2 points are good suggestions.hefest wrote: ↑Feb 01 2020 12:43pmNot sure if this the correct thread to discuss this, but isn't it a bit difficult to keep track of which display firmware version works with tsdz2 firmware version?
Wouldn't it make more sense to use semantic versioning where major and minor versions are the same across the firmwares if they are compatible with each other?
For example, 1.1.X tsdz2 firmware is compatible with any 1.1.x version display firmware?
Another thing that can be improved is configuration. Instead of maintaining it on wiki which already is hard to find valid info on, keep the CONFIGURATION.md in each git branch/tag that corresponds to that version of the software and just maintain the link on Wiki to the MD file?
I think next time I will implement point 1.
Point 2, there is one thing I don't like that makes me not want to do it. As you say, is hard to find the valid info on the wiki and so I try to make the configurations page with a structure and Table of Contents at top of the page - happens that .md files do not support Table of Contents but only the wiki pages when using the Mediawiki style, so, I will keep with that.
On the first point, if you want to keep the major version 0 for some reason, you could use 4 numbers for versioning.