On Sat, Aug 27, 2011 at 3:27 PM, Marc Grue <[email protected]> wrote: > I think Gollum would be a separate repository ("qi4j-docs" ?) on github along > qi4j-core, qi4j-libraries etc. And within that repository (as any github > repository) we could have any branches we want. We could for instance start > out with "2.0" (or "1.4" if necessary), and when that releases then clone the > content of the 2.0 branch to an additional "develop" branch. The develop > branch could then have it's own life, preparing for 2.1, while 2.0 would only > receive bug-fixing. Exactly same approach as the code base.
Well, I would *really* like the docs to be located *with* the source code, as close as possible. That encourages people like Rickard to once in a while add a paragraph or two. In separate repository, that won't happen ;-) I am also quite keen on having docs be generated for offline consumption, and distributed with the SDK itself. >>> 2. How do you suggest that Gollum on www.qi4j.org is tied to the >>> revisions published, incl 'trunk' ? > > Do you mean the developer branch (= 'trunk'?) at github? You want to automate > things, right - can you briefly clarify for me what you want to do? Is it > part of the gradle build? I'm lost... This is 'solved'. Smeagol follows versions via tag names starting with "v", and I assume the 'default' goes against the default branch. > Did you try http://michaelchelen.net/articles/git-wiki-gollum-smeagol.html ? Yes. It complains that some "rack ~> 1.2.0" is required. Gem installed 'rack' and that version was 1.3 something... And in the process I now have a messed up Linux box with unresolved dependencies *sigh*. I hate computers! Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/3xugrbk I work here; http://tinyurl.com/24svnvk I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
