From kato-dev-return-231-apmail-incubator-kato-dev-archive=incubator.apache.org@incubator.apache.org Tue Sep 15 21:14:29 2009 Return-Path: Delivered-To: apmail-incubator-kato-dev-archive@minotaur.apache.org Received: (qmail 68887 invoked from network); 15 Sep 2009 21:14:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Sep 2009 21:14:29 -0000 Received: (qmail 91524 invoked by uid 500); 15 Sep 2009 21:14:29 -0000 Delivered-To: apmail-incubator-kato-dev-archive@incubator.apache.org Received: (qmail 91509 invoked by uid 500); 15 Sep 2009 21:14:29 -0000 Mailing-List: contact kato-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: kato-dev@incubator.apache.org Delivered-To: mailing list kato-dev@incubator.apache.org Received: (qmail 91499 invoked by uid 99); 15 Sep 2009 21:14:29 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Sep 2009 21:14:29 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ant.elder@gmail.com designates 209.85.218.210 as permitted sender) Received: from [209.85.218.210] (HELO mail-bw0-f210.google.com) (209.85.218.210) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Sep 2009 21:14:20 +0000 Received: by bwz6 with SMTP id 6so3024534bwz.12 for ; Tue, 15 Sep 2009 14:13:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=PGy9oN03Lm+35+UqfjWVrmrl5z8l7Ec1bSKHnyyeyAM=; b=CKEKvrzMpWuzisMde8r33GtX/YPUETsHd6Fxn89YlJKD5+mJB9N7/8Tm3luPn39pZl 6e9FbzlnlX9Sf3idRCThyMZw0Jij/UDdtpNKmIyoFqUmsuaYuW0nED96kli+jYQdosLp iBxlHTckpmQQT7rTUC4yEv1TVIE3Gpudi7DD8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type:content-transfer-encoding; b=KnzRdBORfy3Ki1DNsg670TjUQVhVGYJbqpMbOwwitvjnKyOvDTqcCkdPgoHI71bGek NKO3UEJqRiEqrYLPBdDYgoO36mCu/W8Dg4ItcGfVY8ZaRRXgP9zo3sieftvH8q09hFOM pe6vDoZBjG31dU+2z3flWsYfT8TKDxxFDZqRc= MIME-Version: 1.0 Received: by 10.204.8.140 with SMTP id h12mr6745476bkh.204.1253049239539; Tue, 15 Sep 2009 14:13:59 -0700 (PDT) Reply-To: antelder@apache.org In-Reply-To: References: Date: Tue, 15 Sep 2009 22:13:59 +0100 Message-ID: <71e1b5740909151413h4b4831f1p5c1df4797ccbba49@mail.gmail.com> Subject: Re: Release Often, Release Early [WAS Re: First Release, tutorial] From: ant elder To: kato-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Tue, Sep 15, 2009 at 9:27 PM, Robert Burrell Donkin wrote: > On Tue, Sep 15, 2009 at 4:59 PM, Stuart Monteith wro= te: > > > >>>>>>> I was wondering what people (esp. mentors) =A0thought about that. T= he >>>>>>> code >>>>>>> itself would be like an alpha release. =A0This would hopefully enco= urage >>>>>>> discussion and early adoption, and possible participation. >>>>>>> >>> >>> release often, release early :-) >>> >>> i don't know the code but IMHO it's worthwhile thinking about whether >>> 'alpha' is really the best description >>> >>> for example, IMHO >>> >>> * kato-1.0-alpha implies that 1.0 is pretty much done but the code >>> hasn't had the real life testing required to be sure that the quality >>> is there. once an alpha is shipped, i would expect the code to be >>> stable, with just bug fixes until a 1.0 >>> * kato-0.1 implies that kato is short of features and is not mature as >>> an API but that the code quality is reasonable as far as it goes >>> * kato-M1 implies that kato is immature and under very active >>> development but that this milestone offers an island of stability >>> >>> >> >> That last option is the most promising, I'll follow up with what I think= we >> should do. > > IIRC apache harmony uses milestones. might be worth taking a look at > how they do it... > > - robert > We're using Mx type releases in Tuscany for the new version two code, but i've used the other namings for other releases too. There is not really a precise definition of what they mean and what I've found is that which ever you choose someone wont like it or will think it implies the wrong thing, so just pick something and once you start doing releases it doesn't matter so much and you can always change the naming as things progress. I do encourage "release often, release early", having a binary available really can help make it easy for other developers to get going, doing a release will help establish a build structure and the development of a release process, and its going to take some attempts to get a release that will pass through the Incubator voting so better to start now while there's no particular time pressure. ...ant