public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Matt Whitlock <bip@mattwhitlock.name>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Going to tag 0.9.2 final
Date: Fri, 13 Jun 2014 16:06:51 -0400	[thread overview]
Message-ID: <2452920.6eTIu8sTlD@crushinator> (raw)
In-Reply-To: <2420822.WsmHDRmLtl@1337h4x0r>

On Friday, 13 June 2014, at 9:24 pm, xor wrote:
> On Friday, June 13, 2014 12:18:37 PM Wladimir wrote:
> > If I do not hear anything, I will do a
> > last-minute language import
> 
> High risk projects as Bitcoin should NOT see ANY changes between release
> candidates and releases.
> 
> You can cause severe havoc with ANY changes. Humans make mistakes!
> Please do not do such things!

Agreed. Does Bitcoin Core not have a release cycle policy? Typically mission-critical projects will enter a code and resource freeze prior to tagging a release candidate, after which point only critical bugfixes are allowed into the release branch. A language translation update does not qualify as a critical bugfix and should be merged during the next release cycle.



  reply	other threads:[~2014-06-13 20:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-13 10:18 [Bitcoin-development] Going to tag 0.9.2 final Wladimir
2014-06-13 11:21 ` Pavel Janík
2014-06-13 11:58   ` Wladimir
2014-06-13 12:02     ` Pavel Janík
2014-06-13 19:24 ` xor
2014-06-13 20:06   ` Matt Whitlock [this message]
2014-06-13 20:12   ` Jeff Garzik
2014-06-14  5:28     ` Wladimir
2014-06-14  5:42       ` Un Ix
2014-06-14  5:49         ` Matt Whitlock
2014-06-14  5:58           ` Un Ix
2014-06-14  6:01             ` Mark Friedenbach
2014-06-14  6:12             ` Wladimir
2014-06-14  6:23         ` Wladimir

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=2452920.6eTIu8sTlD@crushinator \
    --to=bip@mattwhitlock.name \
    --cc=bitcoin-development@lists.sourceforge.net \
    /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