Release 3.0.0 #95
Release 3.0.0 #95
Conversation
metadata.json
Outdated
| @@ -1,6 +1,6 @@ | |||
| { | |||
| "name": "puppet-windowsfeature", | |||
| "version": "3.0.0-rc0", | |||
| "version": "2.1.1", | |||
There was a problem hiding this comment.
Sorry if I said it wrong or in a confusing way; if the new release will be 3.0.0, set the version to 3.0.0, then let the Travis release task bump to 3.0.1-rc0 directly in master.
There was a problem hiding this comment.
Sorry, my mistake, thought it was already on 2.1.1.
There was a problem hiding this comment.
https://github.com/voxpupuli/puppet-windowsfeature/blob/v2.1.0/metadata.json#L32 << Since that was the last Puppet 3 release, we do need to go to 3.0.0.
|
Bumped metadata.json according to our supported version of puppet for vox |
|
Removed HISTORY.md. @wyardley |
|
Why did you remove the HISTORY.md? Looking at the changelog, you used it when running github-changelog-generator? By then removing it, the next time the changelog task is run, the pre 3.0.0 versions will get overwritten. |
|
@TraGicCode You were right about |
Working on cutting a new release again.
1.) There exist 2 bug fixes since the last release. Does this means we perform 2 patch releases? 1 for each bug fix or is a single patch release okay to contain 2 bug fixes?
2.) Do i need to do any massaging of the changelog titles?