airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Suresh Marru <sma...@apache.org>
Subject Re: Airavata 0.6 release plan
Date Thu, 10 Jan 2013 21:25:16 GMT
I agree as well. Lets defer all the issues outstanding issues to 0.7 and later. I am + 1 for
start preparing for the release. If we wait longer we will budge too many features at once.

Suresh

On Jan 10, 2013, at 1:53 PM, Lahiru Gunathilake <glahiru@gmail.com> wrote:

> On Thu, Jan 10, 2013 at 1:52 PM, Amila Jayasekara
> <thejaka.amila@gmail.com>wrote:
> 
>> On Thu, Jan 10, 2013 at 1:18 PM, Suresh Marru <smarru@apache.org> wrote:
>>> Hi Ate,
>>> 
>>> Thank you for taking time to review the issues and reminding the JIRA.
>> With the delayed release schedules we haven't been effectively using the
>> JIRA's. I think we have to set a fixed time for the releases and call out
>> for coding sprints and streamline this process a bit.
>>> 
>>> Saminda, since you are the RM, I will defer to your call on the issues
>> to be addressed vs deferred to 0.7 release. I will review them too, but it
>> will be early tomorrow.
>> 
>> I think we have  considerable amount of features added to scheduled
>> 0.6. Therefore I think we should release if there are no any
>> showstoppers. All other Jira's should be scheduled for future
>> releases. So I guess we should increase the priority of Jiras which
>> needs to go into release.
>> 
> +1
> 
> Lahiru
> 
>> 
>> Thanks
>> Amila
>> 
>>> 
>>> Suresh
>>> 
>>> On Jan 10, 2013, at 10:02 AM, Ate Douma <ate@douma.nu> wrote:
>>> 
>>>> Hi team,
>>>> 
>>>> I'm not involved really right now, so please take my comments below for
>> what it is worth :)
>>>> 
>>>> Regarding the 0.6 release plan: aren't there a bit too many issues
>> still outstanding for 0.6 (22)? Or are those intended to be move to 0.7+?
>>>> 
>>>> Unrelated, but IMO much more important is the yet unscheduled
>> AIRAVATA-396.
>>>> Its depending on AIRAVATA-406 which is scheduled for 1.0, but maybe
>> that shoud be regarded as kind of unscheduled too?
>>>> I do think this issue however is rather important, even if not a
>> functional one, so would suggest bumping its priority.
>>>> 
>>>> Kind regards, Ate
>>>> 
>>>> On 01/09/2013 03:21 PM, Suresh Marru wrote:
>>>>> Hi All,
>>>>> 
>>>>> Glad to see lots of activity and testing going on. Can we wrap the
>> release? I think we are in a  good shape and we can probably do one RC and
>> a testing marathon and see how it looks. Saminda as you volunteered as a RM
>> of this release, will you be able to follow the instructions on [1] and
>> steer the release?. Please add a [TESTING] prefix to the RC email so it
>> will be easy to manage and pay attention.
>>>>> 
>>>>> Cheers,
>>>>> Suresh
>>>>> 
>>>>> [1] - http://airavata.apache.org/development/release-management.html
>>>>> 
>>>>> 
>>>>> On Nov 7, 2012, at 2:37 PM, Saminda Wijeratne <samindaw@gmail.com>
>> wrote:
>>>>> 
>>>>>> Main features targeted for 0.6 release so far,
>>>>>> 
>>>>>> 1. Registry Rest Service API
>>>>>> The Registry Service API will be the same as Registry API in Airavata
>> 0.5.
>>>>>> It will have JSON support to handle the complex objects.
>>>>>> 
>>>>>> 2. Security framework for Airavata web services
>>>>>> This is the first introduction of a security framework for working
>> with
>>>>>> Airavata system. For 0.6 we will have this security framework applied
>> to
>>>>>> the Registry Rest service. Currently supporting authentication
>> mechanisms
>>>>>> based on above framework are the following,
>>>>>> 
>>>>>>  - Basic Authentication [shipped as the default configuration with
h2
>>>>>>  back-end]
>>>>>>  - Session Authentication
>>>>>> 
>>>>>> 
>>>>>> Comments, suggestions, additions are welcome....
>>>>>> 
>>>>>> Regards,
>>>>>> Saminda
>>>>> 
>>>> 
>>> 
>> 
> 
> 
> 
> -- 
> System Analyst Programmer
> PTI Lab
> Indiana University


Mime
View raw message