Discussion #2162

How to deal with corrigenda to TGs

Added by Michael Lutz over 6 years ago. Updated almost 6 years ago.

Status:Feedback
Priority:Normal
Assignee:Michael Lutz
INSPIRE Theme:

Description

How should small errors that are being found TG docs (e.g. in some Annex I TGs, the URIs for identifying the specifications still contain a rc1-version number) be handled?

  1. Should new versions of the documents (with a bug fix version number, e.g. version 3.1.1) be published, or
  2. Should such corrigenda should be collected and published on a web site and linked to from the TG document with a statement such as "known corrigenda can be found at this link"

History

#1 Updated by Michael Lutz over 6 years ago

Option 2 would be much easier to implement and it would be clearer to the reader what exactly has changed from one version to the next (without having to publish a detailed change log).

In addition, the collected corrigenda could be checked at regular intervals (once every 6 months or 1 year) to see if they would warrant a new version of the document.

Also available in: Atom PDF