Re: Deleting ruby and dotnet top level directories (was Re: 0.12 release update - RC1 this week)
On 07/13/2011 07:15 PM, Chuck Rolke wrote: 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. Done. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Deleting ruby and dotnet top level directories (was Re: 0.12 release update - RC1 this week)
On 07/12/2011 01:47 PM, Gordon Sim wrote: On 07/12/2011 12:18 PM, Robbie Gemmell wrote: Given that we voted to stop releasing standalone artifacts for the pure ruby client with the last release, is there any reason to keep it in the repository? I noticed that the first thing that happened with the 0.10 release was that a user came looking for the ruby client when the artifact went missing, found the code in the 'full release' archive instead, and just used that. A highly effective removal. I have said in the past I'd prefer to use a non-trunk attic area, but the concensus was to go for deletion, although nothing has happened since that discussion. I'm happy to delete this and the dotnet directory. Any objections to that? Going once, going twice... I'll delete these directories tomorrow AM unless I hear objections. I'll do so on both the 0.12 release branch and on trunk. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Deleting ruby and dotnet top level directories (was Re: 0.12 release update - RC1 this week)
On 07/13/2011 08:20 AM, Gordon Sim wrote: Going once, going twice... I'll delete these directories tomorrow AM unless I hear objections. I'll do so on both the 0.12 release branch and on trunk. My only suggestion would be to delete everything in the directories except the top level directory and then place a text / readme in the top level directory telling users where to locate the new versions of these clients. Carl. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Deleting ruby and dotnet top level directories (was Re: 0.12 release update - RC1 this week)
On 07/13/2011 04:39 PM, Carl Trieloff wrote: On 07/13/2011 08:20 AM, Gordon Sim wrote: Going once, going twice... I'll delete these directories tomorrow AM unless I hear objections. I'll do so on both the 0.12 release branch and on trunk. My only suggestion would be to delete everything in the directories except the top level directory and then place a text / readme in the top level directory telling users where to locate the new versions of these clients. I'm not keen on that. Documentation on what we have and where to find it is certainly good. I don't like readmes in stale directories. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Deleting ruby and dotnet top level directories (was Re: 0.12 release update - RC1 this week)
On 07/13/2011 11:53 AM, Gordon Sim wrote: On 07/13/2011 04:39 PM, Carl Trieloff wrote: On 07/13/2011 08:20 AM, Gordon Sim wrote: Going once, going twice... I'll delete these directories tomorrow AM unless I hear objections. I'll do so on both the 0.12 release branch and on trunk. My only suggestion would be to delete everything in the directories except the top level directory and then place a text / readme in the top level directory telling users where to locate the new versions of these clients. I'm not keen on that. Documentation on what we have and where to find it is certainly good. I don't like readmes in stale directories. How about a top level readme with a where everything is. 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. Carl. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Deleting ruby and dotnet top level directories (was Re: 0.12 release update - RC1 this week)
On 07/13/2011 06:16 PM, Carl Trieloff wrote: How about a top level readme with a where everything is. Yes, a top level README is reasonable. 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. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
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-subscr...@qpid.apache.org
Re: Deleting ruby and dotnet top level directories (was Re: 0.12 release update - RC1 this week)
On Tue, Jul 12, 2011 at 01:47:07PM +0100, Gordon Sim wrote: I'm happy to delete this and the dotnet directory. Any objections to that? +1 -- Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/ pgpcHs42F54M8.pgp Description: PGP signature
