You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a developing app I was not taking care of the versioning system, but now that this has attracted some attention and users are giving feedback a versioning schema is a must.
Also a simple way to let the user know that a new version is out and must upgrade his setup.
I'm thinking on this: a relaxed Semantic Versioning starting as 1.0.0 with a Changelog in 'keep a changelog' format.
v1.0.0 will feature the new versioning and new version alert and will fix all open issues.
And then some scripting on the hourly script that keep keps uptodate to check for the latest release and if the local one is not the same of the one in the github repo, show a warning on the website to warn the user about a new version.
Let me know your opinion.
The text was updated successfully, but these errors were encountered:
This brings the versioning schema to the table.
As a developing app I was not taking care of the versioning system, but now that this has attracted some attention and users are giving feedback a versioning schema is a must.
Also a simple way to let the user know that a new version is out and must upgrade his setup.
I'm thinking on this: a relaxed Semantic Versioning starting as 1.0.0 with a Changelog in 'keep a changelog' format.
v1.0.0 will feature the new versioning and new version alert and will fix all open issues.
And then some scripting on the hourly script that keep keps uptodate to check for the latest release and if the local one is not the same of the one in the github repo, show a warning on the website to warn the user about a new version.
Let me know your opinion.
The text was updated successfully, but these errors were encountered: