Mailing-List: contact dev-help@river.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@river.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4DF14BCF.5040304@zeus.net.au>
Date: Fri, 10 Jun 2011 08:40:15 +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: Release River 2.2.0
References: <BANLkTimak44sTP0vneg_6=bs7O-UpuUqMw@mail.gmail.com>
	<4DE9012E.4070708@qcg.nl>
	<BANLkTin=A0NV05i8jOidavH1yBA7N5ovvA@mail.gmail.com>
	<4DEC8F50.1030502@zeus.net.au>
	<BANLkTinUJSt+0sfu29qmfEh8SgXwfeDu_A@mail.gmail.com>
	<BANLkTim=NS0iJFuU9Q2X6WRYKXiyUbZYuA@mail.gmail.com>
 <BANLkTin5TP-FLgq0wzJV=dnm9fa6fEqL6Q@mail.gmail.com>
In-Reply-To: <BANLkTin5TP-FLgq0wzJV=dnm9fa6fEqL6Q@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

The artifacts can be found here;

http://people.apache.org/~thobbs/river/


Tom Hobbs wrote:
> Can anyone spare some time to vet the latest artifacts?
>
> On 6 Jun 2011 21:59, "Tom Hobbs" <tvhobbs@googlemail.com> wrote:
>   
>> Right, can voting begin anew now?
>>
>> I'm uploading new version of the release onto my apache site. The old
>> ones having been moved into a "minusReleaseNotes" dir.
>>
>> These ones should be *the* ones. Fingers cross.
>>
>> Cheers.
>>
>> +1
>>
>> On Mon, Jun 6, 2011 at 9:59 AM, Tom Hobbs <tvhobbs@googlemail.com> wrote:
>>     
>>> Hi Peter,
>>>
>>> Thanks for the review.  I'll make the version updates on the trunk and
>>> merge them into the branch and tag.
>>>
>>> I'm currently going through Jira at the moment and seeing what can be
>>> closed.  I'll post a message here asking for confirmation of any that
>>> look closed but haven't been.  I'm getting 503s from Jira right now
>>> though.
>>>
>>> Cheers,
>>>
>>> Tom
>>>
>>> On Mon, Jun 6, 2011 at 9:26 AM, Peter Firmstone <jini@zeus.net.au> wrote:
>>>       
>>>> Hi Tom,
>>>>
>>>> Don't forget to increment the SERVER_VERSION constant in
>>>>
>>>> com.sun.jini.constants.VersionConstants.java for the new release.
>>>>
>>>> Also in the documentation,
>>>> river/trunk/src-doc/static/release-notes/index.html, the River release
>>>> version also has to be incremented, the above file also has a list of
>>>> changes between each release, so I continued that format by adding the
>>>> generated release notes from jira.
>>>>
>>>> There's also a section in the release notes titled Changes by component
>>>> updated for v2.1.2, which are release notes for each component in river,
>>>> last time, I added the changes from jira relevant to each one.
>>>>
>>>> Before going to all this work it's good to review all the issues in
>>>>         
> Jira, to
>   
>>>> see how many can be closed, or postponed.
>>>>
>>>> Platform Dependencies also needs to be changed to Java 5.
>>>>
>>>> Cheers,
>>>>
>>>> Peter.
>>>>
>>>> Tom Hobbs wrote:
>>>>         
>>>>> Oh yes, I've prob forgotten to do that.  Just saved the edits. We do
>>>>>           
> that
>   
>>>>> when back on proper computer.
>>>>>
>>>>> On 3 Jun 2011 16:44, "Sim IJskes - QCG" <sim@qcg.nl> wrote:
>>>>>
>>>>>           
>>>>>> On 03-06-11 17:01, Tom Hobbs wrote:
>>>>>>
>>>>>>             
>>>>>>> Also, in my excitement, I've forgotten gather the Jira release notes
>>>>>>> etc. So that's not been done. I have, however, added to Sim's "How
>>>>>>> to roll a release" page to make things easier next time round.
>>>>>>>
>>>>>>>               
>>>>>> Be sure to commit the changes, if done on the staging server. :)
>>>>>>
>>>>>> --
>>>>>> QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
>>>>>> Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
>>>>>>
>>>>>>             
>>>>>           
>>>>         
>
>