Currently, Tiki Manager lives without a release version, making sometimes hard to understand the version that is being used.
I would like to suggest a Tiki Manager software versioning, and making a release each month (if there are code changes).
The master (should we rename it to main?) would be the release branch, where tags will co-exist.
And on the side, we would have a 'develop' branch, that would hold all the code changes (that are not hotfixes) and released by merging to 'master' by the end of the month.
The tag would be the ending month: 2020.07 (YYYY.MM)
Hotfix tag: 2020.07.1 (YYYY.MM.*)
This strategy also allow, us developers, to use the 'latest' nightly version and found/fix issues before release date.
Feel free to comment or suggest.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
filename | created | hits | comment | version | filetype | ||
---|---|---|---|---|---|---|---|
No attachments for this item |