Difference between revisions of "Puppet/releases"
< Puppet
(→Modules releases) |
(→Puppetlabs releases) |
||
| Line 79: | Line 79: | ||
== Puppetlabs releases == | == Puppetlabs releases == | ||
* From Kilo, some modules are released and [https://forge.puppetlabs.com/approved approved] on https://forge.puppetlabs.com/openstack | * From Kilo, some modules are released and [https://forge.puppetlabs.com/approved approved] on https://forge.puppetlabs.com/openstack | ||
| − | * For Juno and before, some modules were | + | * For Juno and before, some modules were released on https://forge.puppetlabs.com/stackforge |
== How to release Puppet modules == | == How to release Puppet modules == | ||
Revision as of 19:26, 15 October 2015
Contents
Releases Summary
| Module Version | OpenStack Version | OpenStack Version Codename | Community Supported |
|---|---|---|---|
| 2.y.z | 2013.1.x | Grizzly | no |
| 3.y.z | 2013.2.x | Havana | no |
| 4.y.z | 2014.1.x | Icehouse | no |
| 5.z.y | 2014.2.x | Juno | yes |
| 6.z.y | 2015.1.x | Kilo | yes |
| 7.z.y (not released yet) | 2015.2.x | Liberty | yes (current master) |
Modules releases
Puppetlabs releases
- From Kilo, some modules are released and approved on https://forge.puppetlabs.com/openstack
- For Juno and before, some modules were released on https://forge.puppetlabs.com/stackforge
How to release Puppet modules
Steps to release a Puppet moduleː
- Use the spreadsheet to synchronize the work.
- Make sure there is no blocking patch under review (ieː critical bug)
- Update README with the new release codename & version number
- Update CHANGELOG. You can use some tools to easily get git diff between branches.
- Create the stable branch in Gerrit if needed. See "https://review.openstack.org/#/admin/projects/openstack/puppet-XX,branches" (XX is the module name)
- Push the tag and generate Puppetforge artifact. You can use some tools to automate it.
- Update Release table
- Upload the artifact to Puppetlabs forge
- Make public announcement on openstack-dev using [puppet] tag
