Making tagged drafts

Hi folks,

I said I’d make a proposal, I think this is pretty straightforward.

If the CG creates a git tag, say “draft-2025-11-21”, then we take the documents that are published from that commit and we publish them at

  https://qt4cg.org/draft-2025-11-21/specifications/…

This can be automated, but we can also just do it by hand. If we do it a couple of times, it might never be worth the effort to automate.

The normal PR/draft publication process is never going to change those documents, so they’ll be stable. We can add them to the QT4CG home page and users who want to refer to a stable point can point to those.

I think we should do a little cleanup for those drafts. They should have a status section that clearly states that:

1. They are stable drafts that aren’t going to change
2. They represented the consensus of the group when published
3. They are subject to change as consensus evolves
4. Point to the current working drafts

We can create a top-level index in https://qt4cg.org/draft-2025-11-21/
that provides any editorial or status observations that we want to make about the set of documents as a whole.

                                        Be seeing you,
                                          norm

--
Norm Tovey-Walsh
Saxonica

Received on Friday, 10 October 2025 11:29:39 UTC