issues
search
exadra37-versioning
/
explicit-versioning
A specification for Software Releases that care about intentional breaking changes being explicit announced in the versioning schema.
GNU General Public License v3.0
22
stars
5
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Adds precision to the EOS definition's last point
#18
sapioit
opened
3 years ago
0
"Why" example seems to be coming from an erroneous premise
#17
eslachance
closed
4 years ago
1
Ordering Explicit Versions
#16
Nixinova
opened
4 years ago
1
Improve navigation across documents
#15
Exadra37
opened
7 years ago
0
Closes #13 - Added WORKFLOW document.
#14
Exadra37
closed
7 years ago
1
Software Versioning Workflow
#13
Exadra37
closed
7 years ago
0
Closes issue #4 - Added Best Practices for Software Versioning.
#12
Exadra37
closed
7 years ago
2
Closes issue #9 - Add Terms Scope documentation.
#11
Exadra37
closed
7 years ago
1
Issue #8 - Renames first Required Identifier and improves description for all of them.
#10
Exadra37
closed
7 years ago
0
Terms Scope in Explicit Versioning Context
#9
Exadra37
closed
7 years ago
0
Improve Required Identifiers Schema
#8
Exadra37
closed
7 years ago
3
Closes issue #3 - Add Optional Identifiers to the Explicit Versioning specification schema.
#7
Exadra37
closed
7 years ago
10
Adds a bit more persuasion
#6
sapioit
closed
7 years ago
1
Add FAQ document
#5
Exadra37
opened
7 years ago
9
Best Practices for Development and Production Releases
#4
Exadra37
closed
7 years ago
6
Optional Identifiers
#3
Exadra37
closed
7 years ago
10
Making it explicit
#2
sapioit
closed
7 years ago
29
Making it explicit
#1
sapioit
closed
7 years ago
1