Re: postgresql 7.1 - Mailing list pgsql-general

Not if it a new version is released every three to 6 months.  If a new 40
dollar book came out every three months and a lot of the info is rehash of
the previous 3 versions, then no, I wouldn't buy it on every release.  But
if every 3 to 6 months a 10 to 20 dollar "update" is sold, I would probably
purchase that.

As for the CVS like format, I don't see that as a publishable scheme.  If 20
authors are contributing different levels of work, who is the publisher
going to pay?  Unless... a deal is made with the the publisher... the book
is open source also, authors get nothing (except a name credit in the book)
and the publisher prints and ships it.. only worrying about making profit
off the distruiibution... not compensation for the authors.  Might make the
book cheaper also then.

Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
----- Original Message -----
From: "Tim Uckun" <tim@diligence.com>
To: <pgsql-general@postgresql.org>
Sent: Thursday, October 12, 2000 12:07 PM
Subject: Re: [GENERAL] postgresql 7.1


>
> >
> >Versioning changes often as well as new features and revisions of old
ones.
> >Also, compilation issues always change from release to release.  For a
> >publishing company it would be expensive to constantly put out a book for
> >each version that entails everything. Plus, consumers really don't want
to
> >keep buying the same material over and over again.
>
> For publishers new versions mean new profits so they would most likely
just
> keep the status quo.
>
> >For prohjects such as this that have commercial documentation, why don't
> >they have "patches" for printed books also?
>
> Have the book in a three ring binder. With each version sell new "pages"
or
> "chapters" or both. This way the user removes chapter X and reinserts the
> new updates chapter X.
>
> Here is another idea have the book in a CVS like software. This way just
> like software the documentation can be worked on by many people, some
> people have write access and get to approve and proofread  before it gets
> posted. Everybody can just grab the latest snapshot of the doc.
>
> :wq
> Tim Uckun
> Due Diligence Inc. http://www.diligence.com/   Americas Background
> Investigation Expert.
> If your company isn't doing background checks, maybe you haven't
considered
> the risks of a bad hire.