[DOCS-5063] Comment on: "manual/core/write-concern.txt" Created: 20/Mar/15 Updated: 03/Nov/17 Resolved: 20/Mar/15 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Docs Collector User (Inactive) | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | collector-298ba4e7 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Location: http://docs.mongodb.org/manual/core/write-concern/ |
||
| Participants: | |
| Days since reply: | 7 years, 29 weeks ago |
| Description |
|
It is not helpful to read documentation that is out of date, and then see a comment "Changed in version 2.6: A" with information that replaces what I just read. It would be much more useful if this site had an ability to wrap version tags around blocks of text and expose a version filter in the header so we could just view documentation relevant to the version we're reading. On this page, that would mean wrapping the paragraphs in a tag like <version value="<3.0">...</value> where the data only pertains to versions prior to version 3.0. The new information could be either wrapped in a version tag or left visible to old and new users, saying something like "As of version 3.0 users can..." |
| Comments |
| Comment by Emily Hall [ 27/Jul/16 ] |
|
Closed for housekeeping on 7/27/2016 by Emily Hall. |