qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chuck Rolke <cro...@redhat.com>
Subject Re: Deleting ruby and dotnet top level directories (was Re: 0.12 release update - RC1 this week)
Date Wed, 13 Jul 2011 18:15:15 GMT
There already IS a top level README.txt. An edit on that file will go nicely with the deletion
of component directories. Remember to edit the LICENSE and NOTICE files, too.

-Chuck

----- Original Message -----
> From: "Carl Trieloff" <cctrieloff@redhat.com>
> To: dev@qpid.apache.org
> Sent: Wednesday, July 13, 2011 2:02:59 PM
> Subject: Re: Deleting ruby and dotnet top level directories (was Re: 0.12 release update
- RC1 this week)
> On 07/13/2011 01:59 PM, Gordon Sim wrote:
> >> How about a top level readme with a where everything is.
> >
> > Yes, a top level README is reasonable.
> 
> ack, this is a better than my first idea.
> 
> >
> >> I think this is particularly important given the swig bindings as
> >> they
> >> are not that easy to find unless you know what you are looking for.
> >
> > I agree they aren't easy to find. We also need to be clear about
> > what
> > to expect in terms of maturity with these however.
> 
> My comments are related to usability, and finding the pieces in the
> download. It might make more sense to provide maturity indicators on
> the
> download page, we can discuss this and add them with the 0.12 release.
> 
> Carl.
> 
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org


Mime
View raw message