Add docs 3rd try

[csantanapr]

• add rotation for docs
• add a summary for docs release

[knative-prow-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign markusthoemmes after the PR has been reviewed.
You can assign the PR to them by writing /assign @markusthoemmes in a comment when ready.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[csantanapr]

This replaces #10 and #15

[csantanapr]

/assign @vaikas

[csantanapr]

cc @omerbensaadon

[vaikas]

Thanks!
Does the docs rotation need to also be added to release leads, or is the expectation that they only release the docs repo? Reason I ask is that serving/eventing release leads release all the other repos (not limited to eventing RL only doing eventing related repos) and hence they need some ninja powers. Depending on that answer, we might need to adjust some additional steps like this one:
https://github.com/knative/release/blob/main/README.md#after-the-release

Which instructs the current release leads to create a PR like this: knative/community#619

[vaikas]

@julz since you're the release lead for docs for .24

[csantanapr]

Expectation for the release 0.24 is that a person from docs only release docs. In this case @julz

For release 0.25 then the release lead releasing eventing and serving to also release docs.

There should not be any special (ie netlify) permissions to release docs by then. Only the same permissions given to other repos for example create tags, branches, and self approve PRs on the docs repo for the time period of being release lead. And this I believe is automated today we just need to add docs repo as part of the automation granting and removing permission.

[vaikas]

I don't think we want this change? These are the instructions for all the other repos, so I'd think we want to leave them as is.

[evankanderson]

this comment seems unresponded to?

[vaikas]

https://knative.dev/help/maintainer/docs-release-process/
seemed to indicate there's three repos (client?) But I think on slack you said there's four (operator), so I made this fix(?) there:
https://github.com/knative/docs/pull/3631/files

[vaikas]

I think we should remove the now old section that says to skip the docs repo:
https://github.com/knative/release/pull/19/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5R465

And add this whole section there.

[vaikas]

Reasoning why I think it doesn't belong here is because that link has all the (and then some) details (how to cut a branch, etc.) and I personally found it confusing intermingled here because it's entirely different procedure currently. Client stuff that was added recently are steps that are necessary beyond the normal steps so they made sense to be in this section. WDYT?

[rhuss]

What's about splitting the document into two major sections:

• Releasing the code
• Releasing the documentation

And add a top-level ToC highlighting this difference. We then can also just say "release the docs after the code" which also automatically includes all dependencies. I think that makes sense because you are then free in the docs to reference any additional repos (beyond serving and eventing) and you don't have to take care to update this release document. I see the parallelization benefit (starting the docs release before all repositories has been published) as not big enough to introduce this additional maintenance dependency (updating this doc everytime you want to depend on a new repo in the docs)

[rhuss]

Suggested change

	The current process can be summarize in the following:
	The current process can be summarized in the following:

[rhuss]

Suggested change

	To release the documentation for the release follow [docs release process](https://knative.dev/help/maintainer/docs-release-process/)
	To release the documentation follow [docs release process](https://knative.dev/help/maintainer/docs-release-process/)

[rhuss]

Suggested change

	1. Wait for dependent repos to release (today thats /serving and /eventing)
	1. Wait for dependent repos to be released (today that's /serving and /eventing)

[rhuss]

See my comment above, I would suggest making this more prominent and just say: The docs should be released after the code has been released (so that the docs release team does not need to be aware of the details on which repo it depends. E.g. when including examples from r links to the released client tag or client plugins tag, then you would otherwise need to update this instruction here, which can be easily forgotten, too).

Also, as soon as you add a link to released client plugins, you would have to wait anyway until everything is released, as those plugins are the last to be released.

[dprotaso]

@csantanapr release is next week do you want to wrap up this PR so that docs is part of the process

cc @julz who seems to be the docs release shepherd

[knative-prow-robot]

@csantanapr: PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[knative-prow-robot]

@csantanapr: PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[dprotaso]

bump - it's been a month and the new release is almost two weeks out

[vaikas]

@csantanapr Since today is release day, any chance this could get updated to make sure the process is up-to-date? Or, has it been addressed already in some other PR and I missed it?

[dprotaso]

Closing this out since there hasn't been any movement