Discussions of the Parallel Programming book
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: perfbook@vger.kernel.org
Subject: FYI, planning a release this Friday (December 7th)
Date: Mon, 3 Dec 2018 09:32:56 -0800	[thread overview]
Message-ID: <20181203173256.GA2630@linux.ibm.com> (raw)

Hello!

This is really not a big deal, but I am planning to make a release this
Friday, or by the end of the weekend at the latest (Pacific Time).
I really should be doing releases more often, as they are intended not
so much to be an end product, but rather to be a convenience to readers
who would like to see something recent, but who do not wish to install
the LaTeX machinery required to build from source.  In contrast, an
edition is intended to have consistent look and feel and a minimum of
"under construction" sections.  I hope to put out an edition around
the middle of next year (2019).

Being as I am frequently guilty of forgetting this distinction between
release and edition, I have added the following to FAQ.txt.

Thoughts?

							Thanx, Paul

------------------------------------------------------------------------

10.	What is the difference between a "release" and an "edition"?

	A.	A release is a snapshot provided for readers who would
		like something reasonably up to date, but who do not wish
		to install all the pieces of LaTeX required to build one
		themselves.  Every few years, there will be a special
		release with more-consistent look and feel, and with
		fewer (and preferably no) sections under construction,
		and these special releases are called "editions".  Also,
		as noted earlier, each edition has a version that may
		be more easily printed.


                 reply	other threads:[~2018-12-03 17:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181203173256.GA2630@linux.ibm.com \
    --to=paulmck@linux.ibm.com \
    --cc=perfbook@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox