+v2.0

Question

+v2.0

Closed this issue 3 months ago · 8 comments

Note that in the past we have added an indication in the XML documentation as to which release an enhancement was added (e.g. +v1.1, +v2/0) as this makes it easy to see which attributes cannot be used with an earlier version and what has changed without resorting to github etc, Would it not be a good idea to continue doing so?

Answer 1 · 2024-01-08T17:59:35.000Z

that's right @ue71603, that's useful, but that may not be an easy task to add it now... I don't see how to automatically add +v2 to all the changes that were already validated. Do you see an easy way to do it ?

Answer 2 · 2024-01-08T20:26:50.000Z

@Aurige : I think we can't do it automatically. But we can:

start doing it
perhaps when @trurlurl helps with the documentation we can add it in a PR that updates it in parallel (like we will do with the search for typos).

Answer 3 · 2024-01-11T17:40:55.000Z

Fine for me

Answer 4 · 2024-01-17T14:29:12.000Z

Group decision: yes try to bring this back ! Only for new attribute/element (not on updates)

Answer 5 · 2024-01-17T14:30:06.000Z

Update XSD while updating the document (@trurlurl )

Answer 6 · 2024-01-17T14:35:13.000Z

Also update the NeTEx version in file's header (only if there are some changes)

Answer 7 · 2025-01-12T14:33:08.000Z

Quite some work has been done in #762, #764, #781, #799. This improves the situation at the level of the element annotations and the documentation, but to a lesser extent in the headers. The headers don't seem to be a very reliable source of information to me - and wouln't they be somehow redundant (if they were up to date) to the changelog?
@Aurige Shall we close this issue? Some action or reminder needed regarding headers?

Answer 8 · 2025-01-17T13:59:59.000Z

I thinks that we can close it since a quite huge amount a work has been done.
I agree that headers are not always as useful as they should be, but this can be an independent action