A MIDI player fit to my needs.

Versioning change

Fri, 24 Apr 2020 21:12:46 +0000

Starting with the next version of Musewave (v1.3.0) a change to the versioning system will be made.

The new format is v{major}.{minor}.{patch}. {major} will be incremented for very big noticable changes, {minor} will be incremented for generic additions and whatnot and will be reset after {major} is incremented and finally {patch} will be incremented for fixes that don't really add anything new and won't be reset if the others change.

Previously it followed the format of v{major}.{minor}.{build date days}.{build date seconds}. {major} never got incremented and {minor} only got switched from 1.1 to 1.2 for the MidiPlayer to Musewave namechange, I can't recall at what point I changed from 1.0 to 1.1 but that should illustrate the point somewhat. The latter two values followed a long-deprecated build date system from Visual Studio, it kept yelling at me to stop using it and since I wanted to introduce the {patch} field and finally abided!

This change should hopefully make Musewave's versioning more meaningful.

Sidenote! PowerShell is horrendous. Since I no longer have the build date in the version number, I now store the build date as a Unix timestamp as an embedded resource and I have a PowerShell script run with the build to do this and it looks awful. Here's the script, all it does is "take number and save to file" and it makes it look like some kind of 4d chess.

[string][int][double]::Parse((Get-Date(Get-Date).ToUniversalTime() -UFormat %s)) | Out-File -Encoding ASCII -NoNewline -FilePath $Args[0]