Opened 14 years ago
Closed 13 years ago
#9 closed enhancement (fixed)
Add a nice HTML view of changelogs
Reported by: | ph3-der-loewe | Owned by: | ph3-der-loewe |
---|---|---|---|
Priority: | minor | Milestone: | New Website |
Component: | Website | Version: | |
Keywords: | Cc: | ||
Architecture: | Compiler: | ||
Difficulty: | Kernel: | ||
Operating System: | Parent Tickets: | ||
Patch attached: | no | Protocol: | |
Sound driver: | Topic: | New feature |
Description
On the website there should be a nice HTML view of the changelogs.
The HTML generating script should parse the changelog as sections of lists and add hyperlinks to all kind of URLs and Bug numbers.
Subtickets
Change History (6)
comment:1 Changed 14 years ago by ph3-der-loewe
- Owner set to ph3-der-loewe
- Status changed from new to assigned
comment:2 Changed 14 years ago by shogsbro
comment:3 Changed 14 years ago by shogsbro
If you prefer to stay with an external tool, you can also generate content programattically - see https://bts.keep-cool.org/rpc
comment:4 Changed 13 years ago by ph3-der-loewe
I was thinking about something like what Debian has, for example:
http://packages.debian.org/changelogs/pool/main/r/roaraudio/current/changelog
As direct, gapless integrated element of the website.
However I'm very interested in those features of trac to update the tickets based on commits. I'm very thankful for your description. Is this already active with the current configuration?
comment:5 Changed 13 years ago by ph3-der-loewe
- Milestone set to New Website
comment:6 Changed 13 years ago by ph3-der-loewe
- Resolution set to fixed
- Status changed from assigned to closed
fixed and implemented as part of the daily snapshot process.
Trac has support for automatic updates of tickets from the commit messages, using keywords such as 'closes', 'fixes' etc.
See:
CommitTicketUpdater? — Update tickets based on commit messages.
This component hooks into changeset notifications and searches commit messages for text in the form of:
Instead of the short-hand syntax "#1", "ticket:1" can be used as well, e.g.:
In addition, the ':' character can be omitted and issue or bug can be used instead of ticket.
You can have more than one command in a message. The following commands are supported. There is more than one spelling for each command, to make this as user-friendly as possible.
close, closed, closes, fix, fixed, fixes::
references, refs, addresses, re, see::
A fairly complicated example of what you can do is with a commit message of:
This will close #10 and #12, and add a note to #12.