v2021.3 - 15/09/2021: non-breaking changes

[ghost]

v2021.3 release is scheduled for 15/09/2021 and only includes non-breaking changes, so that any INSPIRE resource passing the test in the previous release automatically passes the same test in this release. This release is the one used for the end-of-year Monitoring process.

Do you use these examples to check if some feature/fix is breaking or non-breaking for metadata conformance classes?

Thanks in advance!

[fabiovin]

Dear @DeordD,

thank you for your question.

For testing purposes, we use a set of resources including the MD examples you mentioned.

You can test your metadata in staging, because, according to the release strategy, between June and September in staging there are only non-breaking changes.

[ghost]

Dear @fabiovin,

I have validated Dataset and Network Service example and both metadata records are valid.

I have asked this question because of the following problems which could lead to "breaking-changes" even though ETS-Rules haven't changed:

• Network Service metadata: (random) error on the coupled resource metadata element (TG Req. 3.6) #515
• Problems with metadata validator #588
• System Error in Executable Test Suite due to redirection system to the INSPIRE registry #525

It means that sometimes metadata-oriented tests for non-breaking changes aren't fully sufficient because of external dependencies, network problems, validator infrastructure, ...

@fabiovin Do you think that above mentioned issues could be potential "non-ETS"-breaking-changes?

P.S.
I am aware it is really complicated to check those things in the structured way.

[ghost]

Hi,

could someone please answer this question?

@fabiovin Do you think that above mentioned issues could be potential "non-ETS"-breaking-changes?

Thanks!