Well, it is a common pain of many OSS projects: development rushes forward, but documentation stays behind.
JBoss configuration changes often. It is not obvious in the Wiki (not only in the post about ClassLoading), which information is general and which is particular just to a certain JBoss version. Like Wikipedia: all posts in Wikipedia have similar structure, so it is more easy dig knowledge from Wikipedia.
I think the Role of Redhat should be to suggest a structure of the posts in the Wiki, so as it will be clear, that:
- what info is general
- what info is particular to a certain version or versions
- what is the difference among verions
- it should be clearly stated, if an author of a post is not sure if her info is general or particular to a certain version of JBoss
Maybe it could be accomplish just by well chosen section and titles, or maybe by special tags/icons in the Wiki.
Ondrej, you're right, some systemic categorization would help.
Wikipedia and JBoss wiki differs in that while the first describes objects and terms of the real world, so most of the articles are general, JBoss wiki articles' "level of generality" goes from "All JBoss products work like this" to "this is how it works for Project AB version XY".
So perhaps we should have similar categories like in JIRA. Using tags is not the best as it's shown at the bottom and rather intended to weave the related articles than to carry the meta-info.
On 20th Jan 2011 we enabled categories for wiki articles at http://community.jboss.org.
Providing project teams have set these up for their spaces you can choose to associate an article with a number of <major>.<minor> releases as shown here:
Click on the 'Filter by Categories and Tags' link in the 'Articles' widget. Categories are specific to a space whereas tags apply across spaces.