From: grarpamp <grarpamp@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] 0.6.x - detachdb in wrong place
Date: Sun, 17 Jun 2012 23:27:52 -0400 [thread overview]
Message-ID: <CAD2Ti28q2_c=AgUjapQQvLLoMcT4ay50q_PuYbwA3820747t1A@mail.gmail.com> (raw)
In-Reply-To: <201206180002.43785.luke@dashjr.org>
> 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
next prev parent reply other threads:[~2012-06-18 3:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-17 9:22 grarpamp
2012-06-17 10:17 ` Gregory Maxwell
2012-06-17 21:35 ` grarpamp
2012-06-17 21:52 ` Gregory Maxwell
2012-06-17 23:04 ` grarpamp
2012-06-18 0:02 ` Luke-Jr
2012-06-18 3:27 ` grarpamp [this message]
2012-06-18 3:57 ` Luke-Jr
2012-06-18 8:09 ` grarpamp
2012-06-18 13:25 ` Luke-Jr
2012-06-20 9:06 ` grarpamp
2012-06-18 0:07 ` Gregory Maxwell
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='CAD2Ti28q2_c=AgUjapQQvLLoMcT4ay50q_PuYbwA3820747t1A@mail.gmail.com' \
--to=grarpamp@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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