You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, it is too redundant & heavy. if it's only a patch version update, there shouldn't be any breaking change introduced, and all latest patch update should be backward compatible. e.g. 2.2.2 schema is able to support 2.2.1 and 2.2.0 as well.
Detailed description:
as above
Describe the solution you'd like
convert the current devfile library to only store schema copy for specific minor versions. and only keep the latest patch schema under each minor version
for example, 2.0.x. 2.1.x and 2.2.x etc.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered:
yangcao77
changed the title
Devfile library should support patch version update
for a single minor version, library should support all previous patches with latest schema
Jun 17, 2024
Which area is this feature related to?
/area library
Which functionality do you think we should add?
for a single minor version, library should support all previous patches with latest schema
Why is this needed? Is your feature request related to a problem?
The current devfile is keeping copies of devfile schema for each patch version:
for example we currently have
2.2.0
,2.2.1
and2.2.2
https://github.com/devfile/library/tree/main/pkg/devfile/parser/data/v2
However, it is too redundant & heavy. if it's only a patch version update, there shouldn't be any breaking change introduced, and all latest patch update should be backward compatible. e.g.
2.2.2
schema is able to support2.2.1
and2.2.0
as well.Detailed description:
as above
Describe the solution you'd like
convert the current devfile library to only store schema copy for specific minor versions. and only keep the latest patch schema under each minor version
for example,
2.0.x
.2.1.x
and2.2.x
etc.Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: