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: <4DE75F1F.10600@zeus.net.au>
Date: Thu, 02 Jun 2011 19:59:59 +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: [VOTE] Release River 2.2
References: <BANLkTi=YD-4NpJ2r1+n=krnoSBfPm8Sitg@mail.gmail.com>
	<BANLkTin7N5xTvRdD1KeGV8jGXYyQb=rJPA@mail.gmail.com>
	<4DE755A6.7020806@zeus.net.au>
 <BANLkTi=F+P6rOwu+bH_WmDC0TVg57wie1A@mail.gmail.com>
In-Reply-To: <BANLkTi=F+P6rOwu+bH_WmDC0TVg57wie1A@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310600&version=12313450

We've also got to increment the release version, or at least check that 
we have, in the source code, I'll have to dig it out of my notes.

In jira we close off any resolved issues and move any remaining out to 
the following release, this way the updated release notes will be 
generated.  Then we've got to edit the documentation too.

After that we can branch the trunk for our release.

Actually I think we have a number of committers and regulars on the dev 
list who been generous with their time contributing or participating.  
However you're instrumental in pushing out a release.

Cheers,

Peter.

Tom Hobbs wrote:
> No worries, Peter.  You've been keeping River afloat on your own plenty.
>
> Can you remember how we generate the release notes out of Jira?
>
> I'm not worried about the duff artifacts, this is what peer reviews are
> for!  "A man who has never made a mistake, has never made anything."
>
> On 2 Jun 2011 10:27, "Peter Firmstone" <jini@zeus.net.au> wrote:
>   
>> Sorry for not being of much assistance recently, River is a tough
>> release, I'll make some time to help tomorrow. Tom has been battling on
>> his own here, keeping the ship on course. Don't worry, I had to throw
>> away my first release artifacts too. A sterling effort.
>>
>> Cheers,
>>
>> Peter.
>>
>> Jukka Zitting wrote:
>>     
>>> Hi,
>>>
>>> On Tue, May 31, 2011 at 10:40 PM, Tom Hobbs <tvhobbs@googlemail.com>
>>>       
> wrote:
>   
>>>> The artifacts can be found here;
>>>>
>>>> http://people.apache.org/~thobbs/river/
>>>>
>>>> Hopefully I've done it all right, if not then please let me know and I
>>>> can get it fixed.
>>>>
>>>>         
>>> -1 The release package doesn't build:
>>>
>>> $ tar zxf apache-river-2.2-src.tar.gz
>>> $ cd apache-river-2.2
>>> $ ant
>>> [...]
>>> BUILD FAILED
>>> .../apache-river-2.2/build.xml:513: .../apache-river-2.2/asm not found.
>>>
>>> Instead of using a script to build the release package, I'd rather
>>> just package up an svn export of the release tag:
>>>
>>> $ svn export http://svn.apache.org/repos/asf/river/jtsk/tags/x.y.z
>>> apache-river-x.y.z
>>> $ tar zcf apache-river-x.y.z.tar.gz apache-river-x.y.z
>>>
>>> This way you'd never have unexpected build problems like the one shown
>>>       
> above.
>   
>>> On a related note, there's no tag for this release. It would be good
>>> if all releases were properly tagged.
>>>
>>> BR,
>>>
>>> Jukka Zitting
>>>
>>>
>>>       
>
>