Post-release RM duties

[Nick Dimiduk <nd...@apache.org>]

Heya,

I noticed tonight that I've been remiss in closing tickets after the dust
settles around a release. I think it's something I/we did, once upon a
time. However, I don't see any mention of it in the ref guide around
releases. Is this something that should be done? Can you point me to our
existing policy on this? I'm happy to go back through and close out
tickets, just give me the affirmative on it being policy we want enforced.

For that matter I don't see much of anything in the way of guidelines for
RMs re: post-release processing. Seems worthy of a new section. I have my
post-VOTE steps outlined at the bottom of my crib sheet [0]. Should I/we
flesh this out in our documentation?

Thanks,
Nick

[0]: https://gist.github.com/ndimiduk/924db7f5ee75baa67802

Re: Post-release RM duties

[Andrew Purtell <ap...@apache.org>]

+1 to at least summarizing the steps in your crib sheet Nick in the online
book.

On Mon, Sep 18, 2017 at 9:13 PM, Nick Dimiduk <nd...@apache.org> wrote:

> Heya,
>
> I noticed tonight that I've been remiss in closing tickets after the dust
> settles around a release. I think it's something I/we did, once upon a
> time. However, I don't see any mention of it in the ref guide around
> releases. Is this something that should be done? Can you point me to our
> existing policy on this? I'm happy to go back through and close out
> tickets, just give me the affirmative on it being policy we want enforced.
>
> For that matter I don't see much of anything in the way of guidelines for
> RMs re: post-release processing. Seems worthy of a new section. I have my
> post-VOTE steps outlined at the bottom of my crib sheet [0]. Should I/we
> flesh this out in our documentation?
>
> Thanks,
> Nick
>
> [0]: https://gist.github.com/ndimiduk/924db7f5ee75baa67802
>



-- 
Best regards,
Andrew

Words like orphans lost among the crosstalk, meaning torn from truth's
decrepit hands
   - A23, Crosstalk

Re: Post-release RM duties

[Sean Busbey <bu...@apache.org>]

Personally, I dislike the "set JIRAs to closed" step, if only because our
jira has a lot of debt and cleaning it up is harder when things are closed.

On Sep 18, 2017 11:13 PM, "Nick Dimiduk" <nd...@apache.org> wrote:

> Heya,
>
> I noticed tonight that I've been remiss in closing tickets after the dust
> settles around a release. I think it's something I/we did, once upon a
> time. However, I don't see any mention of it in the ref guide around
> releases. Is this something that should be done? Can you point me to our
> existing policy on this? I'm happy to go back through and close out
> tickets, just give me the affirmative on it being policy we want enforced.
>
> For that matter I don't see much of anything in the way of guidelines for
> RMs re: post-release processing. Seems worthy of a new section. I have my
> post-VOTE steps outlined at the bottom of my crib sheet [0]. Should I/we
> flesh this out in our documentation?
>
> Thanks,
> Nick
>
> [0]: https://gist.github.com/ndimiduk/924db7f5ee75baa67802
>