Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <grarpamp@gmail.com>) id 1UFyEi-0007H5-Mi
	for bitcoin-development@lists.sourceforge.net;
	Thu, 14 Mar 2013 02:49:44 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.212.49 as permitted sender)
	client-ip=209.85.212.49; envelope-from=grarpamp@gmail.com;
	helo=mail-vb0-f49.google.com; 
Received: from mail-vb0-f49.google.com ([209.85.212.49])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1UFyEg-0004GT-IV
	for bitcoin-development@lists.sourceforge.net;
	Thu, 14 Mar 2013 02:49:44 +0000
Received: by mail-vb0-f49.google.com with SMTP id s24so929563vbi.36
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 13 Mar 2013 19:49:37 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.52.30.170 with SMTP id t10mr319451vdh.4.1363229377003; Wed,
	13 Mar 2013 19:49:37 -0700 (PDT)
Received: by 10.220.115.7 with HTTP; Wed, 13 Mar 2013 19:49:36 -0700 (PDT)
Date: Wed, 13 Mar 2013 22:49:36 -0400
Message-ID: <CAD2Ti28XnZFDLMm+B1cxb5b+adjwk5M-DrFRs7C+VE=SLZ0hNQ@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(grarpamp[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1UFyEg-0004GT-IV
Subject: [Bitcoin-development] Ok to use 0.8.x?
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 14 Mar 2013 02:49:44 -0000

Assuming a new install and first time connection to the net,
is using 0.8.x [1] safe to use, for all (or select?) purposes,
regarding the current fork issue?

If not, is there a recommended branch, tag, or commit, for
all such (or select?) purposes, until such time as an upgrade
alert is broadcasted?

Thanks.

[1] Regarding possible 0.8.x flavors...

There are only 'branch master' and 'tag v0.8.0' here:
https://github.com/bitcoin/bitcoin

There are no 0.8.x branch or tags here yet:
https://git.gitorious.org/bitcoin/bitcoind-stable