Split 1.6 and 2.0 documentation

Registered by Alexey Kopytov

Currently we only have in-source documentation in trunk (which is also published online). However, with new features introduced in 2.0, the documentation will not match 1.6 functionality. So we have to freeze the 1.6 version and publish it separately.

The best way to do it is to backport the doc directory from trunk to 1.6 before adding any 2.0-specific changes to the trunk documentation.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
Alexey Kopytov
Direction:
Approved
Assignee:
Hrvoje Matijakovic
Definition:
Approved
Series goal:
Accepted for 2.0
Implementation:
Implemented
Milestone target:
milestone icon 1.9.1
Started by
Hrvoje Matijakovic
Completed by
Alexey Kopytov

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.