Release Process Plugins » History » Revision 2
Revision 1 (Lukas Zapletal, 08/13/2015 06:03 AM) → Revision 2/3 (Lukas Zapletal, 08/13/2015 11:37 AM)
h1. Release Process for Plugins
h2. Foreman Discovery
h3. Before the release
* Extract strings (http://projects.theforeman.org/projects/foreman/wiki/How_to_Create_a_Plugin#Extracting-strings) (Does not currently work due to https://github.com/theforeman/foreman/pull/2096, workaround solution is to call @make -C locale/ extract update-po@ for a manual extraction as Discovery does not use JavaScript)
* Notify translators about incoming release
* No more i18n-related big changes (new/changed strings)
h3. Release process
* Pull new translations with @make -C locale tx-update@
* Test the develop branch against stable Foreman RC release
* Bump version in @lib/foreman_discovery/version.rb@
* Modify @requires_foreman@ in @engine.rb@
* Git tag and fork @X.Y-stable@ branch
* Build a release with @gem build@
* Investigate contents with @tar -xOf foreman_discovery-x.x.x.gem data.tar.gz | tar -z -list | sort@
* Push to origin including the tag
* Push the release with @gem push@
* Create Jenkins configuration in https://github.com/theforeman/foreman-infra/blob/master/puppet/modules/jenkins_job_builder/files/theforeman.org/yaml/jobs/plugins/foreman_discovery.yaml
* Create packaging requests: https://github.com/theforeman/foreman-packaging/pull/744 and https://github.com/theforeman/foreman-packaging/pull/743 as examples
* Do documentation update: https://github.com/theforeman/theforeman.org/pull/409 (example)