I'm validating Adam's fixes. I should be done with this shortly.
On Fri, Jul 19, 2013 at 5:10 PM, Luke Daley wrote:
> Hi,
>
> Where are we with this? AFAIK we are waiting on some changes from Adam.
>
> --
> Luke Daley
> Principal Engineer, Gradleware
> http://gradleware.com
>
>
> ---
I haven't finished reviewing everything, but it might still be worth doing the
rc-2 now.
On 20/07/2013, at 4:00 AM, Luke Daley wrote:
> That means we are right to release 1.7-rc-2 right?
>
> On 19/07/2013, at 11:42 AM, Szczepan Faber
> wrote:
>
>> Both issues I've checked are now fixed in
On 19/07/2013, at 3:24 PM, Adam Murdoch wrote:
>
> I haven't finished reviewing everything, but it might still be worth doing
> the rc-2 now.
I'd rather wait.
>
> On 20/07/2013, at 4:00 AM, Luke Daley wrote:
>
>> That means we are right to release 1.7-rc-2 right?
>>
>> On 19/07/2013, at
Both issues I've checked are now fixed in the release branch.
On Fri, Jul 19, 2013 at 6:58 PM, Szczepan Faber <
szczepan.fa...@gradleware.com> wrote:
> I'm validating Adam's fixes. I should be done with this shortly.
>
>
> On Fri, Jul 19, 2013 at 5:10 PM, Luke Daley wrote:
>
>> Hi,
>>
>> Where a
That means we are right to release 1.7-rc-2 right?
On 19/07/2013, at 11:42 AM, Szczepan Faber
wrote:
> Both issues I've checked are now fixed in the release branch.
>
>
> On Fri, Jul 19, 2013 at 6:58 PM, Szczepan Faber
> wrote:
> I'm validating Adam's fixes. I should be done with this short
On 19 July 2013 12:00, Luke Daley wrote:
> That means we are right to release 1.7-rc-2 right?
>
That's my understanding, yes.
>
> On 19/07/2013, at 11:42 AM, Szczepan Faber
> wrote:
>
> > Both issues I've checked are now fixed in the release branch.
> >
> >
> > On Fri, Jul 19, 2013 at 6:58 PM
Hi,
Where are we with this? AFAIK we are waiting on some changes from Adam.
--
Luke Daley
Principal Engineer, Gradleware
http://gradleware.com
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/ma
Hi,
We will be doing a second RC.
At this point the following changes will be made:
1. Make the duplicate file message when copying/archiving less intrusive (not
know what the new message will be yet)
2. Explicitly using a duplicate strategy of include disables duplicate warnings
3. Fix TestRe