Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airavata.apache.org
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Airavata 0.12 discussion
From: Suresh Marru <smarru@apache.org>
In-Reply-To: <5374D5E2.4090701@iu.edu>
Date: Mon, 19 May 2014 16:00:15 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <5668388A-763D-4C86-A6C3-7DA5D8A9950D@apache.org>
References: <5374D5E2.4090701@iu.edu>
To: Airavata Dev <dev@airavata.apache.org>

Hi Marlon,

Good lists of targets and thoughts. I do  not have a strong opinion on =
any one, but thinking out, I am favoring June 11th target. It is not =
idea to delay but we have gone on this is exception path of too long, =
atleast better to finish it on a good note.=20

How about we target June 11th for a development freeze of current =
capabilities and release 0.12. And we follow up 3+ weeks later with a =
0.13 release on July 9th? And focus on 0.13 on no new features or code =
additions but a rigorous testing on 0.12 and make a bug fix release?=20

What ever dates we all agree upon, lets set them in stone and sprint =
towards them (atleast for 0.12 and 0.13 and get back to rhythm).

Suresh

On May 15, 2014, at 10:57 AM, Marlon Pierce <marpierc@iu.edu> wrote:

> We've delayed the 0.12 release for some months because it represents a
> significant change (using Apache Thrift for the API, a =
reimplementation
> of the Registry, the initial design of the Application Catalog).=20
> Significant testing  of the Thrift API has exposed lots of problems, =
but
> we are resolving them and making progress.
>=20
> It is time to begin thinking about a release again, and I'd like to =
see
> us get back into our release stride.  Possible release dates to =
target:
>=20
> * May 28th: the Application Catalog won't be ready but we can work
> around this. This may be too soon, however, and some of us have =
external
> constraints (a tutorial at CCGrid 2014).  Putting together the release
> would be distracting.
>=20
> * June 4th: preliminary application catalog should be in better shape,
> release in general should be in better shape, and we will have put it
> through some pretty rigorous testing.
>=20
> * June 11th: Code will be in even better shape, but it is not our
> release philosophy to delay.  I'd like to get back into the release
> stride as soon as possible.
>=20
> Thoughts?
>=20
> Marlon
>=20