-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Best Practices for Development and Production Releases #4
Comments
if we need to create a how to use file, we are making the system too complicate |
The how to use is just to recommend best practices in using it and is in a separated file with exactly the purpose of not cluttering the README that must be only related with establishing the specifications. And maybe a better title would be |
@Exadra37 you mean https://software-development-guidelines.github.io/CMSver/VERSIONING.html |
No that is not what I have in mind. I will describe best practices for versioning when:
|
In other words, practical examples of it's usage, to maximize the percentage of readers that/who completely gasp the concept. |
I will try to outline the best practices to use Explicit Versioning in several stages of the life cycle of Software Development. Some people hate to read or just read in the diagonal and then start posting questions that clearly show they have not payed attention to what they were reading. This type of people learn/grasp better with practical examples and having a guide for Best Practices with some examples will help them and others to completely grasp the concept of Explicit Versioning as you @sapioit wisely have said ;) |
Due to this comment it will be good to create a separated documentation file with examples how to use Explicit Versioning for Development releases and Production Releases.
Maybe something like
how-to-use.md
file should then be linked from the Specification in the README.The text was updated successfully, but these errors were encountered: