-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
What changes should go into the 0.2.5 release? (End of Sept release) #1187
Comments
(I'll be updating this comment as I check more items from the list) Checked items:
Questions:
|
Yeah. Tell me about it. I kind of gave up last month on being surgical and just merged everything. That lead to merging something that shouldn't have been merged. I would not have known it wasn't supposed to be merged, though. I think we need the authors, or at least someone familiar with the change to make the call on whether it should be backported. It would be nice if we added a flag to PRs to say whether we want to backport or not, but right now, there's no way to enforce that.
After discussing a bit yesterday, I'm of the opinion we just want to back port bug fixes to dashing at this point. Eloquent is not that far away, and Dashing is usable, so we don't need to back port features |
I think that's typically what OSRF recommends anyhow. I don't necessarily subscribe to that mentality, but there's too much entropy in this project and its not a good use of your time to try to knit-pick features as you've mentioned. 👍 for back porting genuine bugs only |
Seeing this list I agree. |
I submitted a PR #1193 directly to the dashing devel branch as a bug fix that needs to be merged before 0.2.5 |
Any of my commits for patching the CI should be fine, given they don't intersect with the nav2 code. It could help keep the CI consistent when testing PRs for backporting to dashing. Though, I may need to tweek the docker hooks on the dashing branch to switch the executor image from ros2 nightly to dashing. |
@ruffsl - can you check the boxes above for the commits you want backported?
It would be great if you could fix the CI on the dashing branch! 👍 |
@crdelsey #1198 was merged, should I do a release? |
closing and doing release |
This is the set of commits that have gone into master since the 0.2.4 release. What commits should go into 0.2.5?
The text was updated successfully, but these errors were encountered: