php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #44395 FR: custom changelog parsing
Submitted: 2008-03-10 17:23 UTC Modified: 2012-04-06 18:01 UTC
From: philip@php.net Assigned:
Status: Wont fix Package: Doc Build problem
PHP Version: Irrelevant OS:
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please — but make sure to vote on the bug!
Your email address:
MUST BE VALID
Solve the problem:
8 - 2 = ?
Subscribe to this entry?

 
 [2008-03-10 17:23 UTC] philip@php.net
Description:
------------
This feature request allows us to configure which ChangeLog entries are displayed (built) by PhD.

For example, we may say "Do not show changelog entries earlier than 4.1.0"

This only takes into account changelog roles inside function documentation for now, but should allow future types of changelog markup too.


Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2008-03-11 00:48 UTC] ezyang@php.net
A related, but more complex feature request, would be to have PhD discard parts of documentation that are not pertinent to a version; thus docs can contain info for things in CVS HEAD, while we build against the latest stable version of PHP. This would probably need some extra markup.
 [2008-05-04 00:34 UTC] bjori@php.net
I don't think PhD can sanely discard changelog rows based on magic entry value.
It would make more sense if we used some attributes which we could then compare against.
Something like <entry version="5.2.0">Introduced foobar</entry> could easily be dropped by PhD, or magically create the "version" field in the changelog table.

This can also be solved with JS by collapsing all entries based on the "configured setting"...

 [2009-09-25 18:30 UTC] philip@php.net
Interesting. Added a version="" attribute anywhere sounds potentially 
useful on many levels, but may cause problems on others. Let's think 
about it.
 [2012-04-06 18:01 UTC] bjori@php.net
I don't think this is every going to happen
 [2012-04-06 18:01 UTC] bjori@php.net
-Status: Analyzed +Status: Wont fix
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Sat Apr 20 03:01:28 2024 UTC