On Mon, Jan 19, 2009 at 9:05 PM, Aidan Skinner <[email protected]> wrote:
> On Mon, Jan 19, 2009 at 10:07 PM, Rajith Attapattu <[email protected]> > wrote: > > > I agree with your comments. At the end of the day what matters is end > user > > experience. > > So having something work out of the box is definitely a huge plus. > > Having more granular release artifacts seems like a reasonable approach. > > I am massively +1 on this. I would imagine that the appropriate > breakdown is something like: > > (C++/Java) (Client / Broker) > (Python/Ruby) Client > WSDM->QMF bridge > JMX-GUI > JMX-CLI > For C++ we are only releasing source and not binaries, so a client/broker distinction doesn't make sense. The rest looks good to me. (I assume by JMX-GUI you meant the eclipse pluggins) > > - Aidan > -- > Apache Qpid - World Domination through Advanced Message Queueing > http://qpid.apache.org > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > > -- Regards, Rajith Attapattu Red Hat http://rajith.2rlabs.com/
