Greetings,
A few people just got into a discussion on IRC about how the Matahari manual is developed and versioned. Right now, it's in the same repository with the code. Now that we have a v0.4 branch, we need to decide between two options:
1) Develop and version the manual just like the code.
2) Have a single version of the manual, and ensure that documentation for new features (post v0.4) indicates the version they were first introduced. With this option, we'd just move the documentation into its own repository to avoid any confusion.
Having one version of the manual to maintain is certainly easier, so I'm thinking we should take option #2 until we feel like there is a really good reason to branch the manual.
If there are no objections, I'll get things moved around next week.
Thanks,
On 09/02/2011 09:20 AM, Russell Bryant wrote:
Greetings,
A few people just got into a discussion on IRC about how the Matahari manual is developed and versioned. Right now, it's in the same repository with the code. Now that we have a v0.4 branch, we need to decide between two options:
Develop and version the manual just like the code.
Have a single version of the manual, and ensure that documentation
for new features (post v0.4) indicates the version they were first introduced. With this option, we'd just move the documentation into its own repository to avoid any confusion.
Having one version of the manual to maintain is certainly easier, so I'm thinking we should take option #2 until we feel like there is a really good reason to branch the manual.
If there are no objections, I'll get things moved around next week.
Done. The manual is now here:
https://github.com/matahari/matahari-manual
matahari@lists.fedorahosted.org