exadra37-versioning/explicit-versioning

Best Practices for Development and Production Releases

Exadra37 opened this issue · 6 comments

Exadra37 commented

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.

colomet commented

if we need to create a how to use file, we are making the system too complicate

Exadra37 commented

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 best-pratices.md.

Exadra37 commented

@colomet

No that is not what I have in mind.

I will describe best practices for versioning when:

  • we start Development in a repository from scratch 0.0.0.0 until it becomes Production ready 1.0.0.0.
  • we need to versioning for Development after 1.0.0.0.
  • we need to tag a new release.
sapioit commented

In other words, practical examples of it's usage, to maximize the percentage of readers that/who completely gasp the concept.

Exadra37 commented

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 ;)