Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: esme-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-Id: <24615612.231531235388674356.JavaMail.servlet@kundenserver>
From: Darren Hague <dhague@fortybeans.com>
To: <esme-dev@incubator.apache.org>
Subject: Re: Sprints don't work (was: Sprint 1 Results)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Date: Mon, 23 Feb 2009 12:31:14 +0100

+1 - In my day job, I just create point releases (XX_0.1, XX_0.2, etc) to m=
atch the sprint numbers.

- Darren

>On Mon, Feb 23, 2009 at 10:01 AM, Hirsch, Richard
><richard.hirsch@siemens.com> wrote:
>> Currently, ESME doesn't have any version. We just have "Unscheduled"
>> D.
>
>Yes, but you could define version numbers to match the sprints...you
>don't need to release each of them, but maybe tagging them in
>subversion might be useful.
>
>Just my 2 cents though.
>
>-Bertrand
>
>>
>> -----Urspr=C3=BCngliche Nachricht-----
>> Von: bdelacretaz@gmail.com [mailto:bdelacretaz@gmail.com] Im Auftrag von=
=20
>Bertrand Delacretaz
>> Gesendet: Montag, 23. Februar 2009 09:58
>> An: esme-dev@incubator.apache.org
>> Betreff: Re: Sprints don't work (was: Sprint 1 Results)
>>
>> On Tue, Feb 10, 2009 at 11:52 PM, Darren Hague <dhague@fortybeans.com>=
=20
>wrote:
>>> I like the idea of a hybrid model - namely, every planned feature & tas=
k=20
>goes into JIRA,
>>> but we choose and tag a set of primary & secondary tasks for the curren=
t=20
>sprint. ...
>>
>> +1, and maybe the JIRA versions management feature can be used to
>> choose this set of primary and secondary tasks.
>>
>> -Bertrand
>>


--=20
darren.hague@fortybeans.com