Define the term "Feature"

[EdDev]

Is your feature request related to a problem? Please describe:
The work on the feature lifecycle proposal [1] has raised a request to define and clarify the term "feature".

[1] #251

Describe the solution you'd like:
Define and clarify the term "feature" in relation to API and behavior changes in Kubevirt.
As an outcome, contributors and users should know when a change in the project can be named a "feature".

Consider the feature-lifecycle process implications while defining what a feature is.

Describe alternatives you've considered:
N/A

[iholder101]

Nice! 👍

/cc

[kubevirt-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[EdDev]

/remove-lifecycle stale

[kubevirt-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[iholder101]

/remove-lifecycle stale