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

[Melodic] Update maintainers (#2075) #2076

Closed
wants to merge 1 commit into from

Conversation

sloretz
Copy link
Contributor

@sloretz sloretz commented Oct 14, 2020

Cherry-pick backport of #2075

Previous: @dirk-thomas
New: @jacobperron, @mjcarroll, @sloretz

Signed-off-by: Shane Loretzsloretz@openrobotics.org
Signed-off-by: Shane Loretz sloretz@osrfoundation.org

Previous: @dirk-thomas
New: @jacobperron, @mjcarroll, @sloretz

Signed-off-by: Shane Loretz<sloretz@openrobotics.org>
Signed-off-by: Shane Loretz <sloretz@osrfoundation.org>
@sloretz sloretz self-assigned this Oct 14, 2020
@dirk-thomas
Copy link
Member

I strongly suggest not to backport individual commits out of order but follow the process described in #1496.

@sloretz
Copy link
Contributor Author

sloretz commented Oct 14, 2020

I strongly suggest not to backport individual commits out of order but follow the process described in #1496.

As in backports to older distros should be done periodically in big batches like #1477? Is this what that process looks like?

  1. [Noetic] Update maintainers #2075 should be included in the next Noetic release
  2. After some soak time it should be included in a batch of backports from Noetic -> Melodic
  3. The backports should be released to Melodic
  4. After some soak time the backports should be included in a batch from Melodic -> Kinetic
  5. The backports should be releasd to Kinetic

Does the process have a gap between merging a PR and releasing it, or merging backports and releasing them?

@dirk-thomas
Copy link
Member

Is this what that process looks like?

Correct.

Does the process have a gap between merging a PR and releasing it, or merging backports and releasing them?

That is up to you and the confidence you have that it doesn't break anything. A longer soak time allows you to catch regressions in e.g. Noetic before even backporting and releasing a change into Melodic.

@sloretz sloretz closed this Oct 14, 2020
@sloretz sloretz deleted the melodic-devel_maintainers branch October 14, 2020 18:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants