public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Marcel Jamin <marcel@jamin.net>
To: Btc Drak <btcdrak@gmail.com>
Cc: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] Fwd:  Bitcoin Core 0.12.0 release schedule
Date: Thu, 1 Oct 2015 11:41:25 +0200	[thread overview]
Message-ID: <CAAUq4861Wd2c42gVy7SoW9414R8RGY+Yzp7rDtzagrwQewnFWg@mail.gmail.com> (raw)
In-Reply-To: <CAAUq484+g89yD+s7iR_mGWPM3TTN7V6-EPb1ig=P1BKfcbztPg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 727 bytes --]

---------- Forwarded message ----------
From: Marcel Jamin <marcel@jamin.net>
Date: 2015-10-01 11:39 GMT+02:00
Subject: Re: [bitcoin-dev] Bitcoin Core 0.12.0 release schedule
To: Btc Drak <btcdrak@gmail.com>


I guess the question then becomes why bitcoin still is <1.0.0

I'd say it's safe to say that it's used in production.

2015-10-01 11:17 GMT+02:00 Btc Drak <btcdrak@gmail.com>:

> On Thu, Oct 1, 2015 at 10:05 AM, Marcel Jamin via bitcoin-dev <
> bitcoin-dev@lists.linuxfoundation.org> wrote:
>
>> Any particular reason bitcoin versioning doesn't follow the SemVer spec?
>>
>
> We do: a.b.c, the next major version is, 0.12.0, and maintenance releases
> are 0.12.1 etc. Release candidates are 0.12.0-rc1 for example.
>

[-- Attachment #2: Type: text/html, Size: 1620 bytes --]

  parent reply	other threads:[~2015-10-01  9:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24 11:25 [bitcoin-dev] Bitcoin Core 0.12.0 release schedule Wladimir J. van der Laan
2015-09-29 21:22 ` Jeff Garzik
2015-09-30 17:57 ` Luke Dashjr
2015-09-30 18:10   ` Jorge Timón
2015-09-30 19:24   ` Jeff Garzik
2015-10-01  8:50   ` Wladimir J. van der Laan
2015-10-01  9:05     ` Marcel Jamin
2015-10-01  9:17       ` Btc Drak
     [not found]         ` <CAAUq484+g89yD+s7iR_mGWPM3TTN7V6-EPb1ig=P1BKfcbztPg@mail.gmail.com>
2015-10-01  9:41           ` Marcel Jamin [this message]
2015-10-01  9:56             ` [bitcoin-dev] Fwd: " Wladimir J. van der Laan
2015-10-01 10:10               ` Marcel Jamin
2015-10-01 10:15                 ` Wladimir J. van der Laan
2015-10-01 10:34                   ` Marcel Jamin
2015-10-01 10:50             ` Jeff Garzik
2015-10-01 20:20             ` Luke Dashjr

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=CAAUq4861Wd2c42gVy7SoW9414R8RGY+Yzp7rDtzagrwQewnFWg@mail.gmail.com \
    --to=marcel@jamin.net \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=btcdrak@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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