You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@river.apache.org by Tom Hobbs <tv...@googlemail.com> on 2011/05/31 22:40:38 UTC
[VOTE] Release River 2.2
Okay, since the last effort seemed to be a vote on having a vote, this
is vote on having a release!
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
Re: [VOTE] Release River 2.2
Posted by Tom Hobbs <tv...@googlemail.com>.
In that case, can I make a plea to all and sundry that if you've been
working on Jira issues and have finished them, then please make sure the
issues are closed.
Less work on my end, that way! ;-)
Cheers
On 2 Jun 2011 11:07, "Peter Firmstone" <ji...@zeus.net.au> wrote:
>
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" <ji...@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 <tv...@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
>>>>
>>>>
>>>>
>>
>>
>
Re: [VOTE] Release River 2.2
Posted by Peter Firmstone <ji...@zeus.net.au>.
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" <ji...@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 <tv...@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
>>>
>>>
>>>
>
>
Re: [VOTE] Release River 2.2
Posted by Tom Hobbs <tv...@googlemail.com>.
Cool, thanks. I'll make sure that gets done as well and then roll a new
release.
On 2 Jun 2011 10:49, "Jukka Zitting" <ju...@gmail.com> wrote:
> Hi,
>
> On Thu, Jun 2, 2011 at 11:42 AM, Tom Hobbs <tv...@googlemail.com> wrote:
>> Can you remember how we generate the release notes out of Jira?
>
> See the "Release notes" links in the Roadmap screen [1].
>
> It would be good to make a specific version label for this release.
> You should be able to do that by following the "Manage versions" link
> in the RIVER admin screen [2].
>
> [1]
https://issues.apache.org/jira/browse/RIVER#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel
> [2]
https://issues.apache.org/jira/secure/project/ViewProject.jspa?pid=12310600
>
> BR,
>
> Jukka Zitting
Re: [VOTE] Release River 2.2
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Thu, Jun 2, 2011 at 11:42 AM, Tom Hobbs <tv...@googlemail.com> wrote:
> Can you remember how we generate the release notes out of Jira?
See the "Release notes" links in the Roadmap screen [1].
It would be good to make a specific version label for this release.
You should be able to do that by following the "Manage versions" link
in the RIVER admin screen [2].
[1] https://issues.apache.org/jira/browse/RIVER#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel
[2] https://issues.apache.org/jira/secure/project/ViewProject.jspa?pid=12310600
BR,
Jukka Zitting
Re: [VOTE] Release River 2.2
Posted by Tom Hobbs <tv...@googlemail.com>.
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" <ji...@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 <tv...@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
>>
>>
>
Re: [VOTE] Release River 2.2
Posted by Peter Firmstone <ji...@zeus.net.au>.
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 <tv...@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
>
>
Re: [VOTE] Release River 2.2
Posted by Sim IJskes - QCG <si...@qcg.nl>.
On 03-06-11 10:20, Tom Hobbs wrote:
> Yeah, I'll take a look and keep a proper diary of the exact commands
> etc I use. That'll include when I do the Jira-dance and get the
> release notes sorted.
Post the notes, and i will put them on the webpage.
Gr. Sim
--
QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
Re: [VOTE] Release River 2.2
Posted by Tom Hobbs <tv...@googlemail.com>.
Yeah, I'll take a look and keep a proper diary of the exact commands
etc I use. That'll include when I do the Jira-dance and get the
release notes sorted.
On Fri, Jun 3, 2011 at 8:21 AM, Sim IJskes - QCG <si...@qcg.nl> wrote:
> Tom,
>
> could you have a look if it builds when the 'ant release' method is
> followed?
>
> Gr. Sim
>
>
> On 02-06-11 11:20, Tom Hobbs wrote:
>>
>> Thanks for the feedback, I'll try and get it sorted this evening (GMT).
>>
>> On 2 Jun 2011 10:11, "Jukka Zitting"<ju...@gmail.com> wrote:
>>>
>>> Hi,
>>>
>>> On Tue, May 31, 2011 at 10:40 PM, Tom Hobbs<tv...@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
>>>
>
>
> --
> QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
> Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
>
release procedure
Posted by Sim IJskes - QCG <si...@qcg.nl>.
http://river.staging.apache.org/building-a-release.html
Gr.
--
QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
Re: [VOTE] Release River 2.2
Posted by Sim IJskes - QCG <si...@qcg.nl>.
Tom,
could you have a look if it builds when the 'ant release' method is
followed?
Gr. Sim
On 02-06-11 11:20, Tom Hobbs wrote:
> Thanks for the feedback, I'll try and get it sorted this evening (GMT).
>
> On 2 Jun 2011 10:11, "Jukka Zitting"<ju...@gmail.com> wrote:
>> Hi,
>>
>> On Tue, May 31, 2011 at 10:40 PM, Tom Hobbs<tv...@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
>>
--
QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
Re: [VOTE] Release River 2.2
Posted by Tom Hobbs <tv...@googlemail.com>.
Thanks for the feedback, I'll try and get it sorted this evening (GMT).
On 2 Jun 2011 10:11, "Jukka Zitting" <ju...@gmail.com> wrote:
> Hi,
>
> On Tue, May 31, 2011 at 10:40 PM, Tom Hobbs <tv...@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
Re: [VOTE] Release River 2.2
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Tue, May 31, 2011 at 10:40 PM, Tom Hobbs <tv...@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
Re: [VOTE] Release River 2.2
Posted by Peter Firmstone <ji...@zeus.net.au>.
Tom Hobbs wrote:
> Okay, since the last effort seemed to be a vote on having a vote, this
> is vote on having a release!
>
> 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
>
>
Hey that's awesome Tom, I've got a half drafted reply to your last
email, sorry, I've just been so busy I haven't had time to finish it. I
had been thinking that at some point in the future we should also
release the test kit, so people can test various release artifacts on
their hardware, but that's not a big issue.
I'll make some time shortly to assist.
Regards,
Peter.
Re: [VOTE] Release River 2.2
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Wed, Jun 1, 2011 at 12:00 PM, Tom Hobbs <tv...@googlemail.com> wrote:
> I don't know what we do with them. I got no answer on my "vote on a vote"
> thread. Niclas? Jukka? Any ideas?
The licenses are Apache-compatible, so there's no problem including
these files in the release. The LICENSE file already mentions the ASM
license that covers the AbstractDependencyVisitor class, and for
correctness we should include the MIT license of the
ProfilingSecurityManager class there as well.
This isn't a too big issue, so unless any other problems are spotted
with the release I'd just file this as an issue to be fixed in the
next release and proceed with the current release candidate. I'll do a
better review of the release package shortly before casting my vote,
but on first look it seems pretty good. Nice work!
BR,
Jukka Zitting
Re: [VOTE] Release River 2.2
Posted by Tom Hobbs <tv...@googlemail.com>.
I don't know what we do with them. I got no answer on my "vote on a vote"
thread. Niclas? Jukka? Any ideas?
Cheers,
Tom
On 1 Jun 2011 10:54, "Sim IJskes - QCG" <si...@qcg.nl> wrote:
On 31-05-11 22:40, Tom Hobbs wrote:
>
> Okay, since the last effort seemed to be a vote on having a ...
How do we handle those unapproved licenses in those 2 source files? If a
known error (of the rat tool), shall i document this on the website in a
release page?
Gr. Sim
--
QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
Re: [VOTE] Release River 2.2
Posted by Sim IJskes - QCG <si...@qcg.nl>.
On 31-05-11 22:40, Tom Hobbs wrote:
> Okay, since the last effort seemed to be a vote on having a vote, this
> is vote on having a release!
>
> The artifacts can be found here;
>
> http://people.apache.org/~thobbs/river/
How do we handle those unapproved licenses in those 2 source files? If a
known error (of the rat tool), shall i document this on the website in a
release page?
Gr. Sim
--
QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397