Move Release Process pattern to L2 (Structured)

[dgrizzanti]

Closes #491

@spier let me know what you think about the changes I've made to move this to "Structured". Made a few tweaks. Thanks!

[spier]

@robtuley I am a bit tight on time right now. Any chance you could review this PR?

There is a list of possible improvements to the pattern in #491. Comparing this PR to that list would be a good start for a review.

[spier]

Btw the two failing checks "Generate Mindmap" and "Link Check PR" are ok.

The link https://patterns.innersourcecommons.org/p/release-process will only exist once this PR is merged and the new Structured pattern gets published to our online book. Hence immediately after merging the PR, both checks will pass.

[robtuley]

I can look at this either this evening or tomorrow.

[robtuley]

This looks good to me, the pattern deserves structured status as it has come together really nicely. Looking back at #491 it covers all those areas.

[robtuley]

Last step before merge -- @dgrizzanti any thoughts on title before it gets harder to change it?

Standard Release Process and Published Artifacts

Bit long perhaps? Is "Published Artifacts" unnecessary in the title -- i.e. it is part of the release process? Could switch to "Standard Release Process"?

[dgrizzanti]

@robtuley shortening the title sounds good to me. I'll update that. The file name is already the shortened form so that helps 🙂

[dgrizzanti]

@robtuley should be all set to merge with the updated title!

[spier]

I am changing the points in the associated issue #491 to a checklist, so that we can easier "check the list" lol :)

[spier]

Thank you for these improvements @dgrizzanti!

The key thing that I would recommend to update before publishing is the Context section, possibly Forces as well.

The Context section doesn't contain the type of content that the pattern template asks for, yet. The two sections Context and Forces are often the hardest to write for new pattern authors, so I would be more than happy to help you to improve this section.

I am a bit short on time right now but I can try to provide an example of an improved Context section some time this weekend.

[dgrizzanti]

@spier wanted to ping you to see if you had time to review this. Thanks!

[dgrizzanti]

@spier poking on this to see if you had some time to take a look. Thanks!

[spier]

Hi @dgrizzanti. Just wanted to let you know that I did not forget about this thread, even though it may seem that way :)
Really sorry that I have not been able to work on this sooner. We really appreciate your contribution, and hope to get this merged into the main line, for the benefit of everybody.

I have started a review but it is not quite finished yet.

Stay tuned for more, as they say ;)

[spier]

Hi @dgrizzanti. You have amazing stamina to still keep working on this, even though feedback has been so slow. Really sorry about this, this is not the experience that we want for our contributors!

I promise that I will make my best effort to finish my review this week and send along any remaining questions/ideas that I might have.

Thanks again for your work on this! Have a great day.

[spier]

@dgrizzanti thanks for discussing this pattern further.

I had some time right now to put more thoughts in writing. Figured it is better to do a quick version of this that we can talk about, to move this PR forward.

Looking forward to your feedback.

[spier]

FYI I merged main into this branch, to make sure that our spell checker runs correctly over this new pattern. Spelling looks all good :)

[dgrizzanti]

@spier think I addressed all the new comments and cleaned up a few other small things. Take a look when you get a chance and let me know what you think!

[spier]

Thank you for incorporating the feedback.

This looks great now. Let's push it out into the wild, where it can mature further through the contribution of others, shall we? :)

[spier]

@dgrizzanti this pattern is now out in the wild and published in our book:
https://patterns.innersourcecommons.org/p/release-process

Thank you so much for sticking with it and for sharing the concept with the rest of the InnerSource community.

Hopefully other people will pick up on this pattern and use it, as well as contribute their own experiences to the pattern.

As already mentioned, you can expect to be mentioned as the pattern author on our social channels in the coming weeks, and most likely in the September newsletter of the InnerSource Commons as well.

[spier]

Minor note:
The automatic generation of the mindmap is currently broken.
I have to fix that before you can see the changes your pattern show up in the mindmap.

[spier]

Note to self (mostly):
The mindmap got regenerated as a positiv side effect of #568.

i.e. we now got the latest mindmap in our book, which includes the Standard Release Process pattern
https://patterns.innersourcecommons.org/explore-patterns