Create a Deprecation Policy for Harbor

[a-mccarthy]

Is your feature request related to a problem? Please describe.
Our deprecation policy not clear.

Describe the solution you'd like
As a user of Harbor, I'd like a clear way to understand how features of Harbor are deprecated. This includes

• having an opportunity to discuss and give feedback about my use of a feature, and how deprecations will impact me as a user
• easily receive and find information about a feature's deprecation once its been decided to be deprecated
• Be able to read the deprecation policy that will be used for each feature deprecation.

In order to set this up for our community, we should develop a deprecation policy and publish it in the repo. This policy should require things like the following before a feature can be deprecated:

• A proposal is created and accepted by the community in the Community Repo.
• An issue or Github discussion is created where users can provide feedback (if there isn't a proposal)
• Make the community aware of a deprecation proposal via social media, mailing list, community meetings, add to road map, blogs
• Once the deprecation proposal is accepted, it should be scheduled for a release.
• Update the Harbor docs with information about the deprecation, and any migration steps that are available
• A firm timeframe for how long we will support a feature, once we decide to deprecate something. For example - 1 year, 3 releases, etc.

[a-mccarthy]

For visibility, @qnetter @OrlinVasilev @Vad1mo @yanji09. Please tag whoever else would be interested in this issue.

My purpose here is to get a conversation started to hear what folks in the community think about our deprecation policy. I'm not aware of any deprecation policy written for Harbor, but please add a link if there is one.

[OrlinVasilev]

@tianon @goharbor/all-maintainers @goharbor/maintainers

[github-actions]

This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.

[qnetter]

This should be discussed at the next community meeting (and un-staled).

[a-mccarthy]

looks like @qnetter created a proposal for this, goharbor/community#193.

[qnetter]

Completed via goharbor/community#193