Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 56856 invoked from network); 4 Apr 2011 16:27:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 4 Apr 2011 16:27:32 -0000 Received: (qmail 56316 invoked by uid 500); 4 Apr 2011 16:27:31 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 56283 invoked by uid 500); 4 Apr 2011 16:27:31 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 56275 invoked by uid 99); 4 Apr 2011 16:27:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Apr 2011 16:27:31 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of chirino@gmail.com designates 209.85.216.43 as permitted sender) Received: from [209.85.216.43] (HELO mail-qw0-f43.google.com) (209.85.216.43) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Apr 2011 16:27:26 +0000 Received: by qwf6 with SMTP id 6so4305926qwf.2 for ; Mon, 04 Apr 2011 09:27:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=ps8gJqzy7eTqbc5ECKot9T0h2JuxvQ8nuuQrx+p38l0=; b=uoazY94QVIsy3RJXSnxmDZ/6i545W7EO+AeB5RWkrO3LYtpjFJD+7gl9CE3vc5ZZRO V9GgwkDgH3eSHGV+E6JXuq3k/DtTDz0wP8uSB3NA/kdaew5+wsqY/RxuAx8PyRSgDKEO agu7McS4oYUxJJdzAFKI+ifhMMpoMqwgx1R8g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=jE5+iI7GAF3l75cFNCIz27eGuLoO94YxIcMTyoL/HI5gnsewlcpg5GtlsZOY/S2PaP Am1qk3z32V7g0zHUNM+S2o0tcA4IExgWxHIRi7FKt+UGodjDNMPL+8Rme4k+/7r0DGAw TCAU1TcZHBkrm8SF+mU4Y3l09l/S3chikFOTg= MIME-Version: 1.0 Received: by 10.229.49.209 with SMTP id w17mr5810122qcf.170.1301934424996; Mon, 04 Apr 2011 09:27:04 -0700 (PDT) Sender: chirino@gmail.com Received: by 10.229.79.79 with HTTP; Mon, 4 Apr 2011 09:27:04 -0700 (PDT) In-Reply-To: References: Date: Mon, 4 Apr 2011 12:27:04 -0400 X-Google-Sender-Auth: 9mqR7jWm3-vYkSG23ONqBjaHsYw Message-ID: Subject: Re: [VOTE] Release Apollo 1.0 Beta 1 (2nd Attempt) From: Hiram Chirino To: dev@activemq.apache.org Cc: Bruce Snyder Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Bruce that sounds good to me. Apollo is storing it's documentation along with the project under the apollo-website module so that we can keep the documentation versioned in lock step with the project. It also makes it easier to include the same documentation in the binary distribution. Feel free to add more guides :) Regards, Hiram FuseSource Web: http://fusesource.com/ Connect at CamelOne May 24-26 The Open Source Integration Conference On Mon, Apr 4, 2011 at 11:54 AM, Bruce Snyder wrot= e: > On Mon, Apr 4, 2011 at 7:45 AM, Hiram Chirino wr= ote: >> Yeah I guess the gettings started guide is complicated by a couple of >> extra steps. >> >> I think once we implement: >> https://issues.apache.org/jira/browse/AMQ-3267 >> Which is dejan's suggestion, it should become more streamlined. >> >> We could also remove the BDB part, but I'd hesitate to do that because >> the BDB store implementation does provide a much smoother performance >> characteristic than the included JDBM. =A0And one of the first thing >> folks are going to want to do with a new broker is see how it >> performs. >> >> I don't really care if it's called beta or alpha. =A0The reason I picked >> beta is because I don't see us putting any more major features into >> the release. =A0It just needs go through a couple QA cycles to clean out >> bugs / streamline the user experience. > > Agreed, and we should elaborate on those suggested changes so that so > that we are leading folks down a path to success. My advice is that we > provide a series of guides: > > 1) A 'Getting Started With Apollo in 10 Minutes' guide. This guide > serves as the first time user's guide to getting started with Apollo. > It's basically a smoke test for Apollo in your environment. > > 2) A 'How to Make Apollo Screaming Fast in 10 More Minutes' guide. > This guide is focused on improving Apollo's speed. It provides > suggestions on which items to change, how to change them and the > expected benefits of making such changes. > > 3) A 'Diving Deeper With Apollo' guide. This gives people a > thinking-in-Apollo mindset, provides a high level diagram of the > internals, explains extension points, areas to extend, etc. > > We need to provide some dead simple steps to getting started as well > as taking the next steps to dive deeper in . Without this, the > experience winds up being a needle-in-a-haystack chase for new users, > even if they have already used ActiveMQ. I'd really like to see many > different guides get created over time, each with a different focus > (e.g., different app quality of service requirements, different > business areas, different broker environments, etc.). > > Again, I'm very willing to begin working on this stuff. As I dig into > Apollo to learn what it's all about, I can begin to create these > guides on the wiki with the intention that they live and change as > appropriate. These are only some initial suggestions. > > Bruce > -- > perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=3D6-E+G-N>61E );' > > ActiveMQ in Action: http://bit.ly/2je6cQ > Blog: http://bruceblog.org/ > Twitter: http://twitter.com/brucesnyder >