The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com
Document how Forge modules should be versioned
|Assignee:||Ryan Coleman||% Done:|
Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com
This issue is currently not available for export. If you are experiencing the issue described below, please file a new ticket in JIRA. Once a new ticket has been created, please add a link to it that points back to this Redmine ticket.
We’re now pushing http://semver.org/ for Puppet and related projects. Forge modules should follow the same practice.
To that end, we should include documentation on how to properly version modules (with information about SemVer) and make that documentation visible when a user is publishing a module or release.
I suggest we document the how and why of versioning here: http://docs.puppetlabs.com/puppet/2.7/reference/modules_publishing.html
#4 Updated by Ryan Coleman almost 2 years ago
- Subject changed from Documentation should explain the release version number's ordering to Document how Forge modules should be versioned
- Description updated (diff)
- Affected URL set to http://docs.puppetlabs.com/puppet/2.7/reference/modules_publishing.html
Nick, do you still want to be assigned to this or would you prefer I make a pull against modules_publishing.html?
#5 Updated by Nick Fagerlund almost 2 years ago
- Assignee changed from Nick Fagerlund to Ryan Coleman
If you have a pretty good idea what you want in there, I would lovvvve a pull request.
I suggest you make the versioning instructions a new H3 header underneath the “release a new version” section at the bottom.