Prepare 0.9.0#552
Merged
Merged
Conversation
Contributor
Author
|
Holding on to add #553 |
nuclearsandwich
force-pushed
the
prepare-0.9.0
branch
from
1e26421 to
8bd644f
Compare
nuclearsandwich
force-pushed
the
prepare-0.9.0
branch
from
8bd644f to
28207d9
Compare
Contributor
Author
|
Re-written to correct some whitespace changelog and add #553 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This commit should be fast-forwarded rather than merged via GitHub.
The 0.9.0 release has two significant changes: ament (ROS 2) support for RPM spec generation and support for the
ROS_PYTHON_VERSIONdependency conditional.With the latter change, bloom will generate an error when releasing any package into a rosdistro with no
python_versiondefined in the rosdistro index. This is intentional, see #551 for the rationale.