As discussed. :)
Human descriptive URLs rather than "topic3456.html"
Topic URLs should be derived from descriptive information about the topic. If a topic has a url-slug property this can be used to form the url. If the url-slug property is not set, the URL can be derived from the topic title. The topic url-slug property could be pre-populated from the topic title, and could be able to be overridden by the topic author. If a topic title or topic url-slug property is changed, then the url would change. It is important to enforce persistent URLs in published documentation, so the CMS might have to be aware of whether a topic has been published, in order to preserve the persistence of URLs between releases.
Yes, Matt and I had already discussed this before. That's why I just put "As discussed" in the first comment. Sorry you were not in the loop. :)
*** Bug 787532 has been marked as a duplicate of this bug. ***
Fixed in 20120221-1135 There is a new property tag assigned to a topic called Fixed URL (ID 20). When a topic is processed by the docbook builder for the first time, a unique name is stored in this tag based on the title of the topic, like Review_Whats_New_and_Different_in_JBoss_Enterprise_Application_Platform_6. Once the Fixed URL Property Tag is set, it can only be changed by modifying the property tag. Modifying the topic title will not change the Fixed URL Property Tag. This means it is possible, but not trivial, to change the URL that the topic will appear under, and every day edits to the topics will not affect the fixed url. Landing pages also have fixed urls in the form of Migration_Getting_Started.
Does it handle the situation when a topic is removed from a release? For example: http://docs.redhat.com/.../some-topic resolves for v.1.0, but some-topic is deprecated or removed in the version 1.1 release.