The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Bug #3593

Document how Forge modules should be versioned

Added by Igal Koshevoy almost 4 years ago. Updated over 1 year ago.

Status:ClosedStart date:04/20/2010
Priority:NormalDue date:
Assignee:Ryan Coleman% Done:

0%

Category:documentationSpent time:-
Target version:-
Keywords: Affected URL:http://docs.puppetlabs.com/puppet/2.7/reference/modules_publishing.html
Branch:

We've Moved!

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.


Description

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


Related issues

Related to Puppet Forge - Bug #3592: Site should not reinvent version matching and ordering Closed 04/20/2010

History

#1 Updated by Igal Koshevoy almost 4 years ago

  • Status changed from Unreviewed to Accepted

#2 Updated by Igal Koshevoy over 3 years ago

  • Assignee deleted (Igal Koshevoy)

#3 Updated by James Turnbull over 3 years ago

  • Assignee set to Nick Fagerlund

#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.

#6 Updated by Ryan Coleman over 1 year ago

  • Status changed from Accepted to Closed

We’re covering this pretty well now. Sorry for neglecting updates to this ticket.

Also available in: Atom PDF