Re: We might need a better wording for our release page

[Gerardo Ballabio <gerardo.ballabio@gmail.com>]

Hello all, my 2 cents:

Since the goal is to avoid ambiguity, it may be helpful to define
exactly which ambiguities we want to avoid.

As I understand, this started with Andreas' report of a discussion
where he argued that "testing is not a release" (and unstable isn't
either). So this is one piece of information that we want to convey --
and that would seem to rule out such wording as "stable, testing and
unstable may be called suites, versions, distributions *or releases*".

Another question (or bunch of questions) that we're trying to answer
is: which kind of users should run testing, why would they want to,
and what should they expect (e.g., no timely security fixes, no
promise that it won't eat your data, etc.)

Are there other points that we're trying to drive home?

Gerardo