From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] 0.6.x - detachdb in wrong place
Date: Mon, 18 Jun 2012 03:57:11 +0000 [thread overview]
Message-ID: <201206180357.13430.luke@dashjr.org> (raw)
In-Reply-To: <CAD2Ti28q2_c=AgUjapQQvLLoMcT4ay50q_PuYbwA3820747t1A@mail.gmail.com>
On Monday, June 18, 2012 3:27:52 AM grarpamp wrote:
> 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.
Workflow is all new development takes place in master during release windows.
Eventually, those windows close and master is cleaned up and bugfix'd for the
next 0.x release. Occasionally, when 0.N.0 has some problem before the next
release window opens, Gavin will use it to roll a 0.N.1 (and recently even a
0.N.2 and 0.N.2.2). Once the release window for the next 0.N version opens,
I import the (last bugfix-only commit after the final 0.N.M release made in
master) into the stable repository as the 0.N.x branch, and begin applying
backports. When there's significant backports, I'll tag another 0.N.M from the
branch and possibly release Windows binaries. Usually this happens around the
same time as master becomes the next 0.N.0 release.
> 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.
I guess I've been neglecting to update the stable repo with releases tagged in
master. It should be fixed now.
Luke
next prev parent reply other threads:[~2012-06-18 3:57 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
2012-06-18 3:57 ` Luke-Jr [this message]
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=201206180357.13430.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--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