Hi Gunnar, Thanks, and yes, that works for me, though sometimes the boundary between version-dependent and version-independent can be vanishingly small. For example the workflow to install required dependencies and set up the environment for contributing can change from release to release (or build to build). Still, it's easier to change the wiki for this than a committed document.
This document looks very nice! -Carol P. --------------------------------------------------------------- Email: carol.pearson...@gmail.com Twitter: @CarolP222 --------------------------------------------------------------- On Tue, Jan 26, 2016 at 9:54 PM, Gunnar Tapper <tapper.gun...@gmail.com> wrote: > https://drive.google.com/open?id=0BxlwNhWxn8iTX1M3cndCY3JENVU > > Tested from download required packages to running test suites. Incorporated > Hans' comments except echo $0, which I couldn't get to generate meaningful > results. > > I'll be moving this content to the Trafodion wiki and then update the > website to point to wiki content. > > On wiki vs. documents-in-source, I propose a simple rule-of-thumb: > > Version-dependent documentation must be part of the source code, other > documentation goes to the wiki. > > Does that work? > > -- > Thanks, > > Gunnar > *If you think you can you can, if you think you can't you're right.* >
