On 11 November 2010 13:29, Jon Anstey <[email protected]> wrote: > I think this thread is over but I just wanted to agree on a point Johan (and > probably others) made here. > > "Not to mention if you actually fix a bug and submit a patch you could fix > documentation in one feel swoop." > > That is an EXCELLENT point. In the past I've always put off writing any docs > for a code change (bad, I know..) partly because confluence is slow > and cumbersome and also because once the code fix has been made docs seem > lower priority... I think being able to do both in one commit would make doc > updates happen more often. I mean, sometimes it may be just that you renamed > an endpoint URI property so it may be a really simple change to the docs.
+1000. This is particularly handy when you're doing new development in a branch, separate from the last production release & it also lets you easily stage when new developments & their docs are merged into the website & docs for releases. -- James ------- FuseSource Email: [email protected] Web: http://fusesource.com Twitter: jstrachan Blog: http://macstrac.blogspot.com/ Open Source Integration
