Closed agraul closed 5 years ago
I agree that a good version scheme and changelog make sense for other projects. The theme itself has been used for software and wiki for some time and it should be stable for normal usage. So my plan is to:
Cool, if you need help with git or something let me know :+1:
I updated changelog and readme, and released 1.0.0. They can make the Ruby Gem configuration here instead of making a new repository.
This issue has been solved.
Currently the theme gets updated and other projects that want to implement it use an arbitrary commit. I'd like to request some version scheme for releases so other implementations have an easier time using the theme.
GitHub Docs cover the bases of how to create releases, I am also willing to help out with setting this up, but I don't know enough about the development process to be able to decide on releases or a naming/versioning scheme.