Re: [bitcoin-core-dev] 0.13 release schedule moved forward by a month

2016-04-15 Thread Matt Corallo via bitcoin-core-dev
Note that, per policy, soft forks continue to be independent of major releases.

On April 15, 2016 5:14:52 AM PDT, "Wladimir J. van der Laan via 
bitcoin-core-dev"  wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA512
>
>
>According to the meeting discussion on 2016-04-14 I've moved all the
>dates forward by one month.
>See https://github.com/bitcoin/bitcoin/issues/7679
>
>2016-06-01
>- ---
>- - Open Transifex translations for 0.13
>- - Soft translation string freeze (no large or unnecessary string
>changes until release)
>- - Finalize and close translations for 0.11
>
>2016-06-15
>- ---
>- - Feature freeze (bug fixes only until release)
>- - Translation string freeze (no more source language changes until
>release)
>
>2016-07-06
>- ---
>- - Split off `0.13` branch from `master`
>- - Start RC cycle, tag and release `0.13.0rc1`
>- - Start merging for 0.14 on master branch
>
>2016-08-01
>- ---
>- - Release 0.13.0 final (aim)
>
>-BEGIN PGP SIGNATURE-
>Version: GnuPG v1
>
>iQEcBAEBCgAGBQJXENp8AAoJEHSBCwEjRsmmTzwIAJvyqDl1TV62Tg1zffCXzdTA
>eCJaIcfdDtZ7MPvwkPWB4Jy2VGyqCWhzFtRlQMer0aLBfUwskOlJMBA3iqpyN71u
>p2HWHXCbdBHVXxY5vilYF6OHnJDvNaAjK6am/KHqwUven643VxFrFUd+lfx7LNyx
>/Je0RDVzcYDLXcgl3nSfl6kqlfG0jV7QFTUvpCEzuE6+LqQDbzbhOsSWZeGw3nYc
>cJ5VppKIx9BrKNhq6Zv7X5SzNTuwrBC2xSRwayMYH/1POHEbQbL7ldrMsAm02MD/
>Z9YnLOq6R982hJzAf2VA3mOLd8sKJH2Mg/TwBS42P4mNcPNDd1f1wUU2r9YsUNw=
>=6FXE
>-END PGP SIGNATURE-
>___
>bitcoin-core-dev mailing list
>bitcoin-core-dev@lists.linuxfoundation.org
>https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-core-dev

___
bitcoin-core-dev mailing list
bitcoin-core-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-core-dev


[bitcoin-core-dev] 0.13 release schedule moved forward by a month

2016-04-15 Thread Wladimir J. van der Laan via bitcoin-core-dev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512


According to the meeting discussion on 2016-04-14 I've moved all the dates 
forward by one month.
See https://github.com/bitcoin/bitcoin/issues/7679

2016-06-01
- ---
- - Open Transifex translations for 0.13
- - Soft translation string freeze (no large or unnecessary string changes 
until release)
- - Finalize and close translations for 0.11

2016-06-15
- ---
- - Feature freeze (bug fixes only until release)
- - Translation string freeze (no more source language changes until release)

2016-07-06
- ---
- - Split off `0.13` branch from `master`
- - Start RC cycle, tag and release `0.13.0rc1`
- - Start merging for 0.14 on master branch

2016-08-01
- ---
- - Release 0.13.0 final (aim)

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCgAGBQJXENp8AAoJEHSBCwEjRsmmTzwIAJvyqDl1TV62Tg1zffCXzdTA
eCJaIcfdDtZ7MPvwkPWB4Jy2VGyqCWhzFtRlQMer0aLBfUwskOlJMBA3iqpyN71u
p2HWHXCbdBHVXxY5vilYF6OHnJDvNaAjK6am/KHqwUven643VxFrFUd+lfx7LNyx
/Je0RDVzcYDLXcgl3nSfl6kqlfG0jV7QFTUvpCEzuE6+LqQDbzbhOsSWZeGw3nYc
cJ5VppKIx9BrKNhq6Zv7X5SzNTuwrBC2xSRwayMYH/1POHEbQbL7ldrMsAm02MD/
Z9YnLOq6R982hJzAf2VA3mOLd8sKJH2Mg/TwBS42P4mNcPNDd1f1wUU2r9YsUNw=
=6FXE
-END PGP SIGNATURE-
___
bitcoin-core-dev mailing list
bitcoin-core-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-core-dev


[bitcoin-core-dev] Bitcoin Core 0.12.1 released

2016-04-15 Thread Wladimir J. van der Laan via bitcoin-core-dev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Bitcoin Core version 0.12.1 is now available from:

  

Or through bittorrent:

  
magnet:?xt=urn:btih:25c4df2a822e840e972a50a31095632d87efadab=bitcoin-core-0.12.1=udp%3A%2F%2Ftracker.openbittorrent.com%3A80%2Fannounce=udp%3A%2F%2Ftracker.publicbt.com%3A80%2Fannounce=udp%3A%2F%2Ftracker.ccc.de%3A80%2Fannounce=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969=udp%3A%2F%2Ftracker.leechers-paradise.org%3A6969=https%3A%2F%2Fbitcoin.org%2Fbin%2F
 

This is a new minor version release, including the BIP9, BIP68 and BIP112
softfork, various bugfixes and updated translations.

Please report bugs using the issue tracker at github:

  

Upgrading and downgrading
=

How to Upgrade
- --

If you are running an older version, shut it down. Wait until it has completely
shut down (which might take a few minutes for older versions), then run the
installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac) or
bitcoind/bitcoin-qt (on Linux).

Downgrade warning
- -

### Downgrade to a version < 0.12.0

Because release 0.12.0 and later will obfuscate the chainstate on every
fresh sync or reindex, the chainstate is not backwards-compatible with
pre-0.12 versions of Bitcoin Core or other software.

If you want to downgrade after you have done a reindex with 0.12.0 or later,
you will need to reindex when you first start Bitcoin Core version 0.11 or
earlier.

Notable changes
===

First version bits BIP9 softfork deployment
- ---

This release includes a soft fork deployment to enforce [BIP68][],
[BIP112][] and [BIP113][] using the [BIP9][] deployment mechanism.

The deployment sets the block version number to 0x2001 between
midnight 1st May 2016 and midnight 1st May 2017 to signal readiness for 
deployment. The version number consists of 0x2000 to indicate version
bits together with setting bit 0 to indicate support for this combined
deployment, shown as "csv" in the `getblockchaininfo` RPC call.

For more information about the soft forking change, please see


This specific backport pull-request can be viewed at


[BIP9]: https://github.com/bitcoin/bips/blob/master/bip-0009.mediawiki
[BIP68]: https://github.com/bitcoin/bips/blob/master/bip-0068.mediawiki
[BIP112]: https://github.com/bitcoin/bips/blob/master/bip-0112.mediawiki
[BIP113]: https://github.com/bitcoin/bips/blob/master/bip-0113.mediawiki

BIP68 soft fork to enforce sequence locks for relative locktime
- ---

[BIP68][] introduces relative lock-time consensus-enforced semantics of
the sequence number field to enable a signed transaction input to remain
invalid for a defined period of time after confirmation of its corresponding
outpoint.

For more information about the implementation, see


BIP112 soft fork to enforce OP_CHECKSEQUENCEVERIFY
- --

[BIP112][] redefines the existing OP_NOP3 as OP_CHECKSEQUENCEVERIFY (CSV)
for a new opcode in the Bitcoin scripting system that in combination with
[BIP68][] allows execution pathways of a script to be restricted based
on the age of the output being spent.

For more information about the implementation, see


BIP113 locktime enforcement soft fork
- -

Bitcoin Core 0.11.2 previously introduced mempool-only locktime
enforcement using GetMedianTimePast(). This release seeks to
consensus enforce the rule.

Bitcoin transactions currently may specify a locktime indicating when
they may be added to a valid block.  Current consensus rules require
that blocks have a block header time greater than the locktime specified
in any transaction in that block.

Miners get to choose what time they use for their header time, with the
consensus rule being that no node will accept a block whose time is more
than two hours in the future.  This creates a incentive for miners to
set their header times to future values in order to include locktimed
transactions which weren't supposed to be included for up to two more
hours.

The consensus rules also specify that valid blocks may have a header
time greater than that of the median of the 11 previous blocks.  This
GetMedianTimePast() time has a key feature we generally associate with
time: it can't go backwards.

[BIP113][] specifies a soft fork enforced in this release that
weakens this perverse incentive for individual miners to use a future
time by requiring that valid blocks have a computed GetMedianTimePast()
greater than the locktime specified in any transaction in that block.

Mempool inclusion rules currently require