Re: Qpid 0.8 RC2 available for download ** Please Test **
Doh! Totally missed that - fixing it now. -K - Alan Conway acon...@redhat.com wrote: On 11/17/2010 01:57 PM, Ken Giusti wrote: Hi, Per Alan's findings, I've added a (admittedly terse) README.txt to the examples/qmf-console directory on trunk: http://svn.apache.org/viewvc?rev=1036157view=rev http://svn.apache.org/viewvc?rev=1036158view=rev Shall I pull these over to the 0.8 branch? Also, Alan pointed out that the qmf-agent is not included in the release. I've looked into it a bit - there's no automake/cmake/vcproj support for that example. The Makefile is hard-coded, and there is a dependency on the qmf-gen tool in order to build the example schemas. I don't think the omission of the qmf-agent example is a blocker - I'd rather open a JIRA to include it in the next release. I think that's reasonable, but if so we should remove mention of it from the examples README - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
RE: Qpid 0.8 RC2 available for download ** Please Test **
Hi, Today I made a get latest on the v0.8 rc branch. I have seen that the windows installation notes are not up to date: \0.8-release-candidates\qpid\packaging\windows\INSTALL_NOTES.html I hope this info is here correct. Br, Daniel Sack -Original Message- From: Robbie Gemmell [mailto:robbie.gemm...@gmail.com] Sent: Donnerstag, 18. November 2010 15:56 To: dev@qpid.apache.org Subject: Re: Qpid 0.8 RC2 available for download ** Please Test ** I believe svn merge defaults to updating the merginfo for *all* files/dirs below the current merge dir that have previously been merged (and thus have mergeinfo already), just so that it is up to date. I tend to merge the narrowest dir I can and 'svn revert' the mergeinfo changes on any files/dirs that werent actually modified/dont contain files updated by the merge, leaving only the content changes and the mergeinfo change on the files themselves and their containing directories. This is jsut so the diff looks less cluttered, I dont think there is harm in including the extra mergeinfo updates or leaving them out. For svn merge to know that you heve merged a change on a file/dir the file/dir need mergeinfo added to tell it in future that it doesnt need to merge that change again (eg if you specify a range of commits), but the mergeinfo updates for non-changed files/folders only serves to illustrate the merge happened and perhaps aid future svn merge performance. So long as the actual changed files and their containing folder have mergeinfo applied that should be all thats required for a 'proper merge' record to be kept. Robbie On 18 November 2010 14:19, Ken Giusti kgiu...@redhat.com wrote: Hi, Done! http://svn.apache.org/viewvc?view=revisionrevision=1036461 Also: https://issues.apache.org/jira/browse/QPID-2951 One question: after I merged the changes from trunk to my 0.8 branch, I noticed that not only did my changes come over but a number of unrelated files appeared to have their svn:mergeinfo properties changed. Is this expected? The svn docs I found didn't describe this, and a quick google search showed many suggestions to both check them in, and revert them... I just committed the two files that contain my merge changes, leaving the svn:merginfo changes uncommitted unless I hear otherwise. thanks, -K - Robbie Gemmell robbie.gemm...@gmail.com wrote: Hi Ken, Yes, please merge the readme changes across to the branch. Deferring the qmf-agent update seems sensible. Thanks, Robbie On 17 November 2010 18:57, Ken Giusti kgiu...@redhat.com wrote: Hi, Per Alan's findings, I've added a (admittedly terse) README.txt to the examples/qmf-console directory on trunk: http://svn.apache.org/viewvc?rev=1036157view=rev http://svn.apache.org/viewvc?rev=1036158view=rev Shall I pull these over to the 0.8 branch? Also, Alan pointed out that the qmf-agent is not included in the release. I've looked into it a bit - there's no automake/cmake/vcproj support for that example. The Makefile is hard-coded, and there is a dependency on the qmf-gen tool in order to build the example schemas. I don't think the omission of the qmf-agent example is a blocker - I'd rather open a JIRA to include it in the next release. -K - Alan Conway acon...@redhat.com wrote: On 11/14/2010 05:22 PM, Robbie Gemmell wrote: Hi all, Qpid 0.8 RC2 can nowbe found for download at: http://people.apache.org/~robbie/qpid/0.8/RC2/ I tested the C++ package qpid-cpp-0.8.tar.gz on fedora and rhel5 with cluster pre-requisites installed. There's an out of date RELEASE_NOTES file from the M4 release. Do we overwrite that each time or do we have a better way of getting release notes (e.g. from JIRAs)? It is referred to by README.txt so if we remove it we need to update that. No problem with ./configure; make check; make install Started a cluster, did some basic tests, everything looks ok. examples/README.txt had inconsistent line endings, I checked in a fix on 0.8 branch trunk examples/qmf_agent is missing. Its there in the source tree but is missing the makefile magic to put it in the package. examples/qmf_console has no documentation in README.txt - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
RE: Qpid 0.8 RC2 available for download ** Please Test **
Those notes only go in the Windows installer for display after the install finishes. I've updated the notes locally; if I make an installer for 0.8, the updated version will be included. -Steve -- Steve Huston, Riverace Corporation Total Lifecycle Support for Your Networked Applications http://www.riverace.com -Original Message- From: Daniel Sack [mailto:daniel.s...@techtalk.at] Sent: Thursday, November 18, 2010 11:35 AM To: dev@qpid.apache.org Subject: RE: Qpid 0.8 RC2 available for download ** Please Test ** Hi, Today I made a get latest on the v0.8 rc branch. I have seen that the windows installation notes are not up to date: \0.8-release-candidates\qpid\packaging\windows\INSTALL_NOTES.html I hope this info is here correct. Br, Daniel Sack -Original Message- From: Robbie Gemmell [mailto:robbie.gemm...@gmail.com] Sent: Donnerstag, 18. November 2010 15:56 To: dev@qpid.apache.org Subject: Re: Qpid 0.8 RC2 available for download ** Please Test ** I believe svn merge defaults to updating the merginfo for *all* files/dirs below the current merge dir that have previously been merged (and thus have mergeinfo already), just so that it is up to date. I tend to merge the narrowest dir I can and 'svn revert' the mergeinfo changes on any files/dirs that werent actually modified/dont contain files updated by the merge, leaving only the content changes and the mergeinfo change on the files themselves and their containing directories. This is jsut so the diff looks less cluttered, I dont think there is harm in including the extra mergeinfo updates or leaving them out. For svn merge to know that you heve merged a change on a file/dir the file/dir need mergeinfo added to tell it in future that it doesnt need to merge that change again (eg if you specify a range of commits), but the mergeinfo updates for non-changed files/folders only serves to illustrate the merge happened and perhaps aid future svn merge performance. So long as the actual changed files and their containing folder have mergeinfo applied that should be all thats required for a 'proper merge' record to be kept. Robbie On 18 November 2010 14:19, Ken Giusti kgiu...@redhat.com wrote: Hi, Done! http://svn.apache.org/viewvc?view=revisionrevision=1036461 Also: https://issues.apache.org/jira/browse/QPID-2951 One question: after I merged the changes from trunk to my 0.8 branch, I noticed that not only did my changes come over but a number of unrelated files appeared to have their svn:mergeinfo properties changed. Is this expected? The svn docs I found didn't describe this, and a quick google search showed many suggestions to both check them in, and revert them... I just committed the two files that contain my merge changes, leaving the svn:merginfo changes uncommitted unless I hear otherwise. thanks, -K - Robbie Gemmell robbie.gemm...@gmail.com wrote: Hi Ken, Yes, please merge the readme changes across to the branch. Deferring the qmf-agent update seems sensible. Thanks, Robbie On 17 November 2010 18:57, Ken Giusti kgiu...@redhat.com wrote: Hi, Per Alan's findings, I've added a (admittedly terse) README.txt to the examples/qmf-console directory on trunk: http://svn.apache.org/viewvc?rev=1036157view=rev http://svn.apache.org/viewvc?rev=1036158view=rev Shall I pull these over to the 0.8 branch? Also, Alan pointed out that the qmf-agent is not included in the release. I've looked into it a bit - there's no automake/cmake/vcproj support for that example. The Makefile is hard-coded, and there is a dependency on the qmf-gen tool in order to build the example schemas. I don't think the omission of the qmf-agent example is a blocker - I'd rather open a JIRA to include it in the next release. -K - Alan Conway acon...@redhat.com wrote: On 11/14/2010 05:22 PM, Robbie Gemmell wrote: Hi all, Qpid 0.8 RC2 can nowbe found for download at: http://people.apache.org/~robbie/qpid/0.8/RC2/ I tested the C++ package qpid-cpp-0.8.tar.gz on fedora and rhel5 with cluster pre-requisites installed. There's an out of date RELEASE_NOTES file from the M4 release. Do we overwrite that each time or do we have a better way of getting release notes (e.g. from JIRAs)? It is referred to by README.txt so if we remove it we need to update that. No problem with ./configure; make check; make install Started a cluster, did some basic tests, everything looks ok. examples/README.txt had inconsistent line endings, I checked in a fix on 0.8 branch trunk examples/qmf_agent is missing. Its there in the source tree but is missing the makefile magic to put it in the package. examples/qmf_console has no documentation in README.txt
Re: Qpid 0.8 RC2 available for download ** Please Test **
Hi, I've found a minor issue with the Java broker. On Debian the qpid.start script doesn't work: ebo...@sirius:~/qpid-broker-0.8/bin$ ./qpid.start ./qpid.start: line 21: exec: qpid-server: not found I had to replace exec with sh to get it to work. Emmanuel Bourg Le 14/11/2010 23:22, Robbie Gemmell a écrit : Hi all, Qpid 0.8 RC2 can nowbe found for download at: http://people.apache.org/~robbie/qpid/0.8/RC2/ There were no changes from the output for RC1, but the output from running RAT across the 'full release' RC2 archive can be found at the following URL: http://people.apache.org/~robbie/qpid/0.8/0.8rc2_rat_output.txt *Please* take the time to download and try out this release candidate and report your results, such that any additional issues which require addressing before the release can proceed are identified as early as possible. If no issues are reported that require a new RC to be produced, RC2 will be taken to vote by the end of the week. Thanks, Robbie For the record, the changes since RC1 are: - QPID-2674: prevent heartbeats causing segmentation faults - QPID-2940: clean up message-accept records automatically - QPID-2941: fix error in recovery handling for new CLFS store - QPID-2942: enable the Java broker convenience package to be started out-of-the-box - QPID-2943: add the examples to the Java client convenience package - QPID-2946: exclude the QMan convenience package from the release (due to QPID-2945) - Update to always include cluster scripts in the C++ distribution regardless of dependency install status on the build box - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org smime.p7s Description: S/MIME Cryptographic Signature
Re: Qpid 0.8 RC2 available for download ** Please Test **
Here's a quick spot check qpid-0.8.tar.gz. Three things we might want to change ... File: qpid-0.8.tar.gz ###./qpid-0.8 directory: No README.txt or INSTALL in the top-level directory. The user needs an overview that describes which directories contain which component, and points to README.txt and INSTALL in those directories. Where do I start if I want to build a client in a given language or a given broker? ### ./qpid-0.8/cpp directory: README.txt contains a Quick Start that doesn't work, because there is no configure file: 3. Quick start == If you are impatient to get on, ./configure make will usually be sufficient to compile. Running make check will run tests, make install will install the client and daemon. For more detailed information, please see the INSTALL notes. We do ship configure with the cpp distribution. ### ./qpid-0.8/cpp/examples directory: Do we want to continue to ship the old API examples, with no indication that these are using the older API? I would remove them or at least put them in a subdirectory with a name that indicates they do not use the current API. Jonathan P.S. In the ./cpp directory, the build succeeds, and 'make check' does not return any errors. I did this on a box that does not have clustering installed. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Qpid 0.8 RC2 available for download ** Please Test **
The Java client distribution includes a README.txt that has nothing to do with the Java client distribution. It explains how to build and run the broker, but not how to build and run the examples. Jonathan - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
RE: Qpid 0.8 RC2 available for download ** Please Test **
Comments inline. -Original Message- From: Jonathan Robie Sent: 15 November 2010 16:29 Subject: Re: Qpid 0.8 RC2 available for download ** Please Test ** Here's a quick spot check qpid-0.8.tar.gz. Three things we might want to change ... File: qpid-0.8.tar.gz ###./qpid-0.8 directory: No README.txt or INSTALL in the top-level directory. The user needs an overview that describes which directories contain which component, and points to README.txt and INSTALL in those directories. Where do I start if I want to build a client in a given language or a given broker? It's definitely something to add to the list of things we could improve in future (hopefully way before the Release Candidate stage), however this has been the case with every release so far and people seem to have managed to work it out. ### ./qpid-0.8/cpp directory: README.txt contains a Quick Start that doesn't work, because there is no configure file: 3. Quick start == If you are impatient to get on, ./configure make will usually be sufficient to compile. Running make check will run tests, make install will install the client and daemon. For more detailed information, please see the INSTALL notes. We do ship configure with the cpp distribution. This is simply another example of our overall packaging needing work, and an outcome of the fact that we ship 2 different archives with different representations of the same source. I think we should only be shipping 1 copy of any particular source and in case of the cpp tree that should be the 'distribution' version, not the repository copy included in the 'full release' archive as noted above. Another thing to add to the list for improvements, but again no different than the past. ### ./qpid-0.8/cpp/examples directory: Do we want to continue to ship the old API examples, with no indication that these are using the older API? I would remove them or at least put them in a subdirectory with a name that indicates they do not use the current API. I agree they should probably move to a subdirectory in future or just be removed if they are considered truly unsupported API. Jonathan P.S. In the ./cpp directory, the build succeeds, and 'make check' does not return any errors. I did this on a box that does not have clustering installed. I think the comments point out definite areas we can improve in future. I welcome any updates people want to make on trunk to benefit future releases and which can then also be considered for any future required 0.8 RC's, but I don't see anything here warranting a new RC in and of itself as these are not changes to our historical norm. Robbie - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
RE: Qpid 0.8 RC2 available for download ** Please Test **
It's a generic readme file, and points to the documentation for all Java components on the wiki (which, alas, is for now still the best source of information for most of them) before following up with the broker details. Again something to be improved in future (documentation on the Java side is something I intend to look at for the next release). Robbie -Original Message- From: Jonathan Robie [mailto:jonathan.ro...@redhat.com] Sent: 15 November 2010 19:40 To: dev@qpid.apache.org Subject: Re: Qpid 0.8 RC2 available for download ** Please Test ** The Java client distribution includes a README.txt that has nothing to do with the Java client distribution. It explains how to build and run the broker, but not how to build and run the examples. Jonathan - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Qpid 0.8 RC2 available for download ** Please Test **
Hi all, Qpid 0.8 RC2 can nowbe found for download at: http://people.apache.org/~robbie/qpid/0.8/RC2/ There were no changes from the output for RC1, but the output from running RAT across the 'full release' RC2 archive can be found at the following URL: http://people.apache.org/~robbie/qpid/0.8/0.8rc2_rat_output.txt *Please* take the time to download and try out this release candidate and report your results, such that any additional issues which require addressing before the release can proceed are identified as early as possible. If no issues are reported that require a new RC to be produced, RC2 will be taken to vote by the end of the week. Thanks, Robbie For the record, the changes since RC1 are: - QPID-2674: prevent heartbeats causing segmentation faults - QPID-2940: clean up message-accept records automatically - QPID-2941: fix error in recovery handling for new CLFS store - QPID-2942: enable the Java broker convenience package to be started out-of-the-box - QPID-2943: add the examples to the Java client convenience package - QPID-2946: exclude the QMan convenience package from the release (due to QPID-2945) - Update to always include cluster scripts in the C++ distribution regardless of dependency install status on the build box - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
RE: Qpid 0.8 RC2 available for download ** Please Test **
I have tested the following: - JMX Management Console starts on Linux, Windows, OSX - C++ broker can be compiled and started (without clustering) using the qpid-cpp-0.8.tar.gz package. - Java broker package starts, out-of-the-box. - Java client package connects to the broker and sends/receives using the Hello example now included in the package. Robbie P.S. It is still necessary to supply a logging implementation + sl4fj binding to do the last check. I'm looking to remove the need to do so by updating slf4j, which now provides a warning and does No-Op logging by default rather than throwing an exception. I didn't think the change should be included in 0.8 at this point anyway when I raised the JIRA, but I am seeing an odd test failure after making the change which now makes me think that doubly-so: it'll go in soon for 0.9. -Original Message- From: Robbie Gemmell [mailto:robbie.gemm...@gmail.com] Sent: 14 November 2010 22:23 To: dev@qpid.apache.org Subject: Qpid 0.8 RC2 available for download ** Please Test ** Hi all, Qpid 0.8 RC2 can nowbe found for download at: http://people.apache.org/~robbie/qpid/0.8/RC2/ There were no changes from the output for RC1, but the output from running RAT across the 'full release' RC2 archive can be found at the following URL: http://people.apache.org/~robbie/qpid/0.8/0.8rc2_rat_output.txt *Please* take the time to download and try out this release candidate and report your results, such that any additional issues which require addressing before the release can proceed are identified as early as possible. If no issues are reported that require a new RC to be produced, RC2 will be taken to vote by the end of the week. Thanks, Robbie For the record, the changes since RC1 are: - QPID-2674: prevent heartbeats causing segmentation faults - QPID-2940: clean up message-accept records automatically - QPID-2941: fix error in recovery handling for new CLFS store - QPID-2942: enable the Java broker convenience package to be started out-of-the-box - QPID-2943: add the examples to the Java client convenience package - QPID-2946: exclude the QMan convenience package from the release (due to QPID-2945) - Update to always include cluster scripts in the C++ distribution regardless of dependency install status on the build box - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
