This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reason will be displayed to describe this comment to others. Learn more.
Choose a reason
Spam
Abuse
Off Topic
Outdated
Duplicate
Resolved
Low Quality
Can we move it further down in the script? That way it would get through all of the steps and ask to confirm just before committing. Also if we do that maybe change the text to something along the lines of "Generated release tarball at XXX. Proceed to commit to SVN?"
The reason will be displayed to describe this comment to others. Learn more.
Choose a reason
Spam
Abuse
Off Topic
Outdated
Duplicate
Resolved
Low Quality
It would make sense if the script was creating a tarball and performing some complex logic. However, it’s simply copying the existing tarball from dev to release without any tarball manipulation.
I've pushed this update across all other DataFusion repositories. It would make sense to me if we keep tarball-release.sh the same across projects.
If you’re keen on change I’m happy to adapt but I’m feeling a bit stressed about testing it after this morning. 😀
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.
Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low QualityCan we move it further down in the script? That way it would get through all of the steps and ask to confirm just before committing. Also if we do that maybe change the text to something along the lines of "Generated release tarball at XXX. Proceed to commit to SVN?"
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
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.
Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low QualityIt would make sense if the script was creating a tarball and performing some complex logic. However, it’s simply copying the existing tarball from dev to release without any tarball manipulation.
I've pushed this update across all other DataFusion repositories. It would make sense to me if we keep tarball-release.sh the same across projects.
If you’re keen on change I’m happy to adapt but I’m feeling a bit stressed about testing it after this morning. 😀
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.