Documents are always published with the date of the latest build.
This works well for guides and manuals, but is a real problem for SBPs.
Best Practices are not written by us. Quite often there is some "confusion" about the latest updated version, as some authors first work in private repos, before they use our official suse-best-practices repo. Thus we would have to rely on the "publication date" stamp to ensure there is no confusion.
Inside the docs, this problem could be addressed by using the fix date instead of the flexible time stamp. But this is doable only in xml documents, not in asciidoc, because AsciiDoc(tor) assigns the latest build date to the document.
This problem of the time stamp could be avoided if, each time an SBP gets updated for fresh publication, only the updated document would be build and published, instead of the entire repo with all documents.
Documents are always published with the date of the latest build.
This works well for guides and manuals, but is a real problem for SBPs. Best Practices are not written by us. Quite often there is some "confusion" about the latest updated version, as some authors first work in private repos, before they use our official suse-best-practices repo. Thus we would have to rely on the "publication date" stamp to ensure there is no confusion.
Inside the docs, this problem could be addressed by using the fix date instead of the flexible time stamp. But this is doable only in xml documents, not in asciidoc, because AsciiDoc(tor) assigns the latest build date to the document.
This problem of the time stamp could be avoided if, each time an SBP gets updated for fresh publication, only the updated document would be build and published, instead of the entire repo with all documents.