Return-Path: Delivered-To: apmail-incubator-river-dev-archive@minotaur.apache.org Received: (qmail 55963 invoked from network); 3 Oct 2009 09:17:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 3 Oct 2009 09:17:26 -0000 Received: (qmail 21447 invoked by uid 500); 3 Oct 2009 09:17:26 -0000 Delivered-To: apmail-incubator-river-dev-archive@incubator.apache.org Received: (qmail 21383 invoked by uid 500); 3 Oct 2009 09:17:26 -0000 Mailing-List: contact river-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: river-dev@incubator.apache.org Delivered-To: mailing list river-dev@incubator.apache.org Received: (qmail 21373 invoked by uid 99); 3 Oct 2009 09:17:26 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 03 Oct 2009 09:17:26 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [61.9.189.137] (HELO nschwmtas01p.mx.bigpond.com) (61.9.189.137) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 03 Oct 2009 09:17:15 +0000 Received: from nschwotgx03p.mx.bigpond.com ([61.9.223.241]) by nschwmtas01p.mx.bigpond.com with ESMTP id <20091003091652.WGOP3375.nschwmtas01p.mx.bigpond.com@nschwotgx03p.mx.bigpond.com> for ; Sat, 3 Oct 2009 09:16:52 +0000 Received: from [10.1.1.2] (really [61.9.223.241]) by nschwotgx03p.mx.bigpond.com with ESMTP id <20091003091651.LKFW10433.nschwotgx03p.mx.bigpond.com@[10.1.1.2]> for ; Sat, 3 Oct 2009 09:16:51 +0000 Message-ID: <4AC7168F.50201@zeus.net.au> Date: Sat, 03 Oct 2009 19:17:03 +1000 From: Peter Firmstone User-Agent: Thunderbird 2.0.0.14 (X11/20080531) MIME-Version: 1.0 To: river-dev@incubator.apache.org Subject: Re: Release versioning References: <4AC403C5.6000103@zeus.net.au> <4AC4912D.80403@zeus.net.au> <4AC534E3.2080407@zeus.net.au> <4AC6E020.8060601@zeus.net.au> <02D744AE-9053-476D-A479-0678BFF86B11@gmail.com> In-Reply-To: <02D744AE-9053-476D-A479-0678BFF86B11@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-RPD-ScanID: Class unknown; VirusThreatLevel unknown, RefID str=0001.0A150203.4AC71684.004C,ss=1,fgs=0 X-Virus-Checked: Checked by ClamAV on apache.org OK, yes that's a more sensible path. +1 Regards, Peter. Jukka Zitting wrote: > Hi, > > Niclas Hedhman kirjoitti 3.10.2009 kello 7.38: >>> >> And then you end up with the problem of defining "when is a bug fix, >> incompatible change" :-) > > The definition of a bug is behaviour that differs from the documented > or otherwise expected behaviour. > > From that perspective any code that is broken by a bug fix is already > incorrect, and I wouldn't worry too much about such breakage. > > BR, > > Jukka Zitting >