Ben Collins-Sussman <sussman@collab.net> writes:
> Zack Brown <zbrown@tumblerings.org> writes:
>
> > > Fitz, cmpilato and I are in process of rewriting and expanding
> > > chapters 3, 4, and 5 right now. So I'm not sure what our policy is.
> > > I'm not sure if our commits to the book must "always keep the book
> > > perfectly readable". If so, we need to be careful what we commit, or
> > > commit less often, or work on a branch. If not, then we should upload
> > > new PDFs only at major junctures, when the book *is* in a readable
> > > state.
> >
> > I'd suggest having two side-by-side versions for each type (html, pdf,
> > ps). The first version will be the 'careful' one that everyone should
> > read if they just want info. The second version will be the
> > up-to-the-minute one that folks should read if they just want to follow
> > the book's development progress without compiling it themselves.
>
> Well, that implies that fitz, cmpilato, and I should be doing our work
> on a branch. Then somebody (you? :-)) would compile the source from
> both branches and upload them to the site.
Well, I don't have a problem with working on a branch, but we don't do
nightly/weekly binary builds of Subversion itself, so why should we do
so with the documentation?
That said, if someone else wants to do this, then they can go right
ahead. :)
> I'm starting to like the branch idea a lot. But I wonder if people
> really want to see fancy {html, ps, pdf} versions of a book that may
> not be coherent.
No clue. But I'm fine with working on a branch. CVS has taught me to
avoid branches where possible for reasons of pain and suffering. I
continue to do so even though it's a piece of cake in Subversion.
Maybe this would be good 'therapy'. :)
-Fitz
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 6 15:32:21 2002