Mailing-List: contact dev-help@river.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@river.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: <50921D63.4000406@zeus.net.au>
Date: Thu, 01 Nov 2012 16:57:39 +1000
From: Peter Firmstone <jini@zeus.net.au>
User-Agent: Thunderbird 2.0.0.14 (X11/20080531)
MIME-Version: 1.0
To: dev@river.apache.org
Subject: Re: Next Release (PING)
References: 
 <CAEDB+kVTx4gSMc4_4D3+ixLDPCjxnXa7eLm3trtGnWTcoLUb7g@mail.gmail.com>
 <508D450A.6020201@qcg.nl> <508D4588.20805@qcg.nl> <509143E6.9070308@qcg.nl>
In-Reply-To: <509143E6.9070308@qcg.nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Simon IJskes - QCG wrote:
> On 28-10-12 15:47, Simon IJskes - QCG wrote:
>> On 28-10-12 15:45, Simon IJskes - QCG wrote:
>>> On 28-10-12 15:43, Tom Hobbs wrote:
>>>> Can someone refresh my memory, please?  I recall a few months ago we
>>>> were
>>>> talking about gearing up for a release.  Is there any reason why we
>>>> can't
>>>> cut one now-ish?
>>>
>>> none. go for it!
>>
>> Although, what do we do with the failing tests since the URL->URI 
>> commits?
>>
>>
>
>

I recall recently some tests were failing because of spaces in path 
names, but that's what I'd expect; spaces are used as codebase 
delimiters, so failure is correct because the path is incorrectly formatted.

When I was developing URI changes, all tests passed when path names were 
correctly formatted, in fact it solved so many issues that the Windows 
platform can now be supported without cigwin.

If we can find a reason URI code is not standards compliant, then lets 
fix it, but it's up to users for format their paths correctly. I've 
provided a utility class for that purpose.

I do have a suggestion prior to release though, that all new code in 
org.apache.river be separated into org.apache.river.api or 
org.apache.river.impl.

Cheers,

Peter.