I gated the release earlier but this task was long done. Any objections to move forward with 0.16 release?
Suresh > On Mar 30, 2016, at 2:53 PM, Suresh Marru <sma...@apache.org> wrote: > > To contradict my proposal, I would like to work on > https://issues.apache.org/jira/browse/AIRAVATA-1945 > <https://issues.apache.org/jira/browse/AIRAVATA-1945> before requesting > feature freeze. Should not take long. > > Suresh > >> On Mar 28, 2016, at 11:29 AM, Pierce, Marlon <marpi...@iu.edu >> <mailto:marpi...@iu.edu>> wrote: >> >> Do we have any outstanding tasks that need to be wrapped up and committed to >> dev? >> >> From: Shameera Rathnayaka <shameerai...@gmail.com >> <mailto:shameerai...@gmail.com>> >> Reply-To: "dev@airavata.apache.org <mailto:dev@airavata.apache.org>" >> <dev@airavata.apache.org <mailto:dev@airavata.apache.org>> >> Date: Monday, March 28, 2016 at 11:20 AM >> To: Airavata Dev <dev@airavata.apache.org <mailto:dev@airavata.apache.org>> >> Subject: Re: Airavata 0.16 Release Planning >> >> +1 >> >> On Mon, Mar 28, 2016 at 10:50 AM Suresh Marru <sma...@apache.org >> <mailto:sma...@apache.org>> wrote: >>> Hi All, >>> >>> Before we go too far, how about we call a feature freeze and stat working >>> on 0.16 release? Unless any one is in the middle of a development activity, >>> how about we target end of the week to start working on it? >>> >>> Suresh >> >> -- >> Shameera Rathnayaka >