-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement Asciidoctor macros for release notes documents #1082
Labels
Feature
New feature or request
Comments
@sdarwin and @pdimov for this ticket I'll need a new repo e.g. It probably makes more sense that that rubygems account be tied to the c++ alliance/boost than me, and Rob suggested you'd be the people to talk to about that. Can you help? |
@daveoconnor you are an admin of https://github.com/cppalliance/asciidoctor-boost |
daveoconnor
added a commit
that referenced
this issue
Nov 1, 2024
daveoconnor
added a commit
that referenced
this issue
Nov 1, 2024
daveoconnor
added a commit
that referenced
this issue
Nov 8, 2024
daveoconnor
added a commit
that referenced
this issue
Nov 8, 2024
Related to ticket #1082, this adds support for asciidoc macros to emulate macros from qbk. Macro support is documented at https://github.com/cppalliance/asciidoctor-boost/
GregKaleka
pushed a commit
that referenced
this issue
Nov 14, 2024
Related to ticket #1082, this adds support for asciidoc macros to emulate macros from qbk. Macro support is documented at https://github.com/cppalliance/asciidoctor-boost/
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is connected with the new release notes procedure. The current qbk-based mechanism for release notes production makes available some "macros" defined here:
https://github.com/boostorg/website/blob/master/feed/ext.qbk
Many of these macros are not in actual use in the release notes (meaning I haven't seen them used recently or ever). The ones that I've seen are (see the latest qbk-based release notes and the generated output):
[phrase library..XX]
: produces a header for the section on lib X.[@/libs/function/ Function]
creates a link to the docs for the library (Function in the example). I understand that[github_pr geometry 1247]
: produces this: PR#1247[github geometry 1231]
: produces this: #1231[@/tools/build/ Build]
: I think this is formally equivalent to[@/libs/function/ Function]
.We need to have equivalent Asciidoc macros for the benefit of Boost authors contributing their individual notes in the new release notes procedure.
The text was updated successfully, but these errors were encountered: