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
