Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1SgSdD-0001S4-Tm for bitcoin-development@lists.sourceforge.net; Mon, 18 Jun 2012 03:27:59 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.175 as permitted sender) client-ip=74.125.82.175; envelope-from=grarpamp@gmail.com; helo=mail-we0-f175.google.com; Received: from mail-we0-f175.google.com ([74.125.82.175]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1SgSdD-0001Dq-74 for bitcoin-development@lists.sourceforge.net; Mon, 18 Jun 2012 03:27:59 +0000 Received: by werg55 with SMTP id g55so3801934wer.34 for ; Sun, 17 Jun 2012 20:27:53 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.207.27 with SMTP id m27mr6990969weo.42.1339990072991; Sun, 17 Jun 2012 20:27:52 -0700 (PDT) Received: by 10.180.7.105 with HTTP; Sun, 17 Jun 2012 20:27:52 -0700 (PDT) In-Reply-To: <201206180002.43785.luke@dashjr.org> References: <201206180002.43785.luke@dashjr.org> Date: Sun, 17 Jun 2012 23:27:52 -0400 Message-ID: From: grarpamp To: bitcoin-development@lists.sourceforge.net Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.2 (-) 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 0.4 AWL AWL: From: address is in the auto white-list X-Headers-End: 1SgSdD-0001Dq-74 Subject: Re: [Bitcoin-development] 0.6.x - detachdb in wrong place X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2012 03:28:00 -0000 > be sure to have good backups that never touched the new code... > We have at various times had bugs in master that would corrupt > wallets Sorry, that's to be expected, I shouldn't have asked. > It would be very helpful if anyone offering bitcoin services would > setup parallel toy versions of your sites on testnet... Good point. > we don't currently have enough testing activity on master. I usually test compile / report current and stable of things I use. So I get that github/master is the obvious top of things. But in looking at where the tags are between repositories, it's still not clear to me what the workflow is. Example... There are these release tarballs on sourceforge, which all have tags in github, yet no tags in gitorious. There are no 'x' branches on github, yet there is one release applicable branch on gitorious. I guess I'd expect to see, that if as hinted by Luke that gitorious has the stable trees, that there would be release tags there, laid down at some comfy point in time on the 'x' stable branches there. (The stable branches inheriting new code from master). But there are no such tags. And the releases/tags seem to magically appear from nowhere on github :) Again, I'm trying to extricate myself from CVS here. # sourceforge tarballs 0.6.0 0.6.1 0.6.2 0.6.2.2 # github branches remotes/origin/master 432d28d Merge pull request #1477 from gmaxwell/master remotes/origin/0.6.2 40fd689 Bump version to 0.6.2.2 for osx-special build # github tags v0.6.0 v0.6.1 v0.6.2 v0.6.2.1 v0.6.2.2 # gitorius branches remotes/origin/0.6.0.x d354f94 Merge branch '0.5.x' into 0.6.0.x remotes/origin/0.6.x 5e322a7 Merge branch '0.6.0.x' into 0.6.x # gitorious tags v0.6.0.7