-
Notifications
You must be signed in to change notification settings - Fork 206
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
Release #131
Comments
Yes - I've got a couple PRs I want to merge first, then I'll release. I've created a noetic-devel branch so that I could merge the header path changes in #128 . @peci1 are you actively using both melodic and noetic? I'm trying to decide how aggressively I should backport commits from noetic-devel to the indigo-devel branch so that they get released into melodic. (melodic gets released from the inidigo-devel branch) |
Thanks. We're actively using Melodic and will be slowly switching to Noetic, so we're interested in having the changes in both. Melodic still has 2 years of lifetime, so I think it makes sense to backport things. |
Melodic release here: ros/rosdistro#31119 I've updated the source and doc branches to match the branch that is actually released into melodic: kinetic-devel. After that PR gets merged I'll do the noetic release from the new noetic-devel branch. |
Noetic release here: ros/rosdistro#31149. Noetic version numbers are now |
Could I ask for a new Melodic/Noetic release? There seems to have been quite some development since the last one (more than a year now).
The text was updated successfully, but these errors were encountered: