-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rework release preparation tasks #789
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The config_defaults.yml
removal suggestions may become redundant when they are used again. That'll depend on the actual implementation we end up using.
6eb0ccd
to
7cb7284
Compare
7cb7284
to
53e535a
Compare
eeee714
to
1d09e30
Compare
I just synced the modulesync_config repo form vox for one of our modules, with a change to target the development branch of voxpupuli-release: The release which was previously broken is now fixed \o/: |
In this branch we include what is required to validate this two PRs: * voxpupuli/modulesync_config#789 (Synced from this branch) * voxpupuli/voxpupuli-release#44 (Fetch the gem form the WIP branch in git rather than Rubygems)
In this branch we include what is required to validate this two PRs: * voxpupuli/modulesync_config#789 (Synced from this branch) * voxpupuli/voxpupuli-release#44 (Fetch the gem form the WIP branch in git rather than Rubygems)
In this branch we include what is required to validate this two PRs: * voxpupuli/modulesync_config#789 (Synced from this branch) * voxpupuli/voxpupuli-release#44 (Fetch the gem form the WIP branch in git rather than Rubygems)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK provided the changes in voxpupuli-release are released and you bump the lower version bound in config_defaults.yml
:
modulesync_config/config_defaults.yml
Lines 34 to 35 in 514efa7
- gem: voxpupuli-release | |
version: '>= 1.2.0' |
I just opened voxpupuli/voxpupuli-release#51. When merged, i will add a commit to this PR to bump the version requirement and we should be good to go 👍 |
|
@@ -32,7 +32,7 @@ Gemfile: | |||
ruby-version: '2.5' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not blocking for this, but I'm tempted to add the changelog generator as a hard dependency to voxpupuli-release.
f2e71d3
to
72f3684
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's squash the commits.
Could you also open a PR to https://github.com/voxpupuli/puppet-example to verify the changes? Though I assume it's fine, it's better to know for sure.
This is a follow-up to #788 Voxpupuli contributors used to update a module version and `rake changelog` before openning a PR for preparing a new release. Some modules now have a REFERENCE.md file that also needs to be updated (by running `rake reference`), and forgetting to do so will remained unnoticed until `rake release` complain that the file is not up-to-date (so after the release PR was reviewed and merged). This PR remove the `changelog` and `reference` tasks which are now part of the voxpupuli-release gem.
72f3684
to
0dd9814
Compare
In this branch we include what is required to validate this two PRs: * voxpupuli/modulesync_config#789 (Synced from this branch) * voxpupuli/voxpupuli-release#44 (Fetch the gem form the WIP branch in git rather than Rubygems)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Pretty much the last step to minimizing the Rakefile. Just test_with_coveralls
left. That should either be removed, moved to voxpupuli-test or puppetlabs_spec_helper. But that's for another PR.
This is a follow-up to #788
Voxpupuli contributors used to update a module version and
rake changelog
before openning a PR for preparing a new release. Some modules now have a REFERENCE.md file that also needs to be updated (by runningrake reference
), and forgetting to do so will remained unnoticed untilrake release
complain that the file is not up-to-date (so after the release PR was reviewed and merged).This PR remove the
changelog
andreference
tasks which are now part of the voxpupuli-release gem.