Skip to content
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

Start release process creating NOTICE #765

Conversation

danielmitterdorfer
Copy link
Member

With this commit we move the creation of the NOTICE file to the
beginning of the release process. As this depends on pulling files from
repositories that are not under our control, it can fail. By doing this
as the first step, we can correct any errors before other tasks have
modified state.

With this commit we move the creation of the NOTICE file to the
beginning of the release process. As this depends on pulling files from
repositories that are not under our control, it can fail. By doing this
as the first step, we can correct any errors before other tasks have
modified state.
@danielmitterdorfer danielmitterdorfer added enhancement Improves the status quo :misc Changes that don't affect users directly: linter fixes, test improvements, etc. labels Sep 10, 2019
@danielmitterdorfer danielmitterdorfer added this to the 1.4.0 milestone Sep 10, 2019
Copy link
Contributor

@ebadyano ebadyano left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thank you!

@danielmitterdorfer
Copy link
Member Author

Thanks for the review! :)

@danielmitterdorfer danielmitterdorfer merged commit e005dfe into elastic:master Sep 10, 2019
@danielmitterdorfer danielmitterdorfer deleted the create-notice-at-release-start branch September 10, 2019 13:40
novosibman pushed a commit to novosibman/rally that referenced this pull request Oct 2, 2019
With this commit we move the creation of the NOTICE file to the
beginning of the release process. As this depends on pulling files from
repositories that are not under our control, it can fail. By doing this
as the first step, we can correct any errors before other tasks have
modified state.

Relates elastic#765
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improves the status quo :misc Changes that don't affect users directly: linter fixes, test improvements, etc.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants