Skip to content
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

linking trac tickets to individual changes #2

Open
pbiron opened this issue Jun 3, 2017 · 0 comments
Open

linking trac tickets to individual changes #2

pbiron opened this issue Jun 3, 2017 · 0 comments

Comments

@pbiron
Copy link
Owner

pbiron commented Jun 3, 2017

It appears to me that phpdoc-parser and wporg-developer have 2 separate ways attaching trac tickets to specific changes in the core sources:

  1. using @link <url of trac ticket> in docblocks sources.
  2. using the "Attach Ticket" field in the "Parsed Content" meta box when editing a wp-parser-(class|method|function|hook) post

However, to the best of my understanding at this point, neither of these methods links that ticket to a specific @since tag. Therefore, it is not possible to reliably output a trac ticket(s) for each change. Doing so would be very helpful to those writing dev-notes in the weeks leading up to a new WP release.

But that would require changes to how phpdoc-parser and/or wporg-developer stores info in the DB. If/when those changes are made to how info is stored, wp-since will need to be updated to grab that new representation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant