You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by Suresh Marru <sm...@apache.org> on 2013/08/29 15:39:12 UTC
Roadmap to Airavata 1.0
Hi All,
In the last 2 years Airavata has evolved significantly and I feel we are about the time to stabilize the Airavata Access Layer through a API and make a 1.0 release. Here are some thoughts on what we need to do before Airavata can be 1.0:
* Ready to move into semantic versioning of releases
* Have a API which will survive through minor releases and only calls out for API changes for major releases
* Decide upon a going forward SCM among SVN or GIT
* Have well documented client integration examples
* Scrub of any unused dependencies and revisit the latest versions of critical dependencies
* Agree upon supported features
* Remove any third party maven repos (down to 1 as of today)
* Resolve all the issues which are bugs (and preferably improvements as well)
* Revisit all wish style issues and comment on the ones planned to be addressed in near future.
* External review of the project by soliciting developers from fellow apache projects.
Additional thoughts and tasks we need to accomplish before 1.0?
Suresh
Re: [DISCUSS] SVN to GIT for Airavata
Posted by Sanchit Aggarwal <sa...@gmail.com>.
+1 for GIT, mainly beacuse :
- gives individual better local version control, changes can be easily
push back into central repo.
- SVN merge are complicated and error prone, as compared to git which are
less messy and simple.
Regards
Sanchit Aggarwal
On Sat, Sep 21, 2013 at 2:06 AM, Marlon Pierce <ma...@iu.edu> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I'd really like to here from the GSOC students and others on the list
> without SVN write access. Would you find things easier if you could
> easily do a git fork?
>
>
> Marlon
>
> On 9/20/13 3:31 PM, Suresh Marru wrote:
> > Hi All,
> >
> > One of the items we briefly listed on roadmap [1] is deciding on a SCM
> which can go forward. Do we have any strong opinions on SVN Vs GIT? Just
> starting a discussion.
> >
> > Suresh
> > [1] - http://markmail.org/thread/5nq7jfk5b7izbip3
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQEcBAEBAgAGBQJSPLG6AAoJEOEgD2XReDo5v1oH/RViy7qNDQgUmKcxlSM8Yi7d
> f4DFRRG8JzP2QWotwUhkBGSYEPUgyVizg5JNzOxUGRFcTTRsz5GXV3ihursAM+6L
> 4OKJE9jTy3PMKOWjqdYRlpieDs3JbR9omc+Vkb1dOBkfgnS7xNBjPNxtlKheO+K3
> OrjivVKgBdJCu+R3fSGmNfN0X1BGwfPEob8MeMV9prXaXKcl+1MuV175R+hB5eMO
> dgBoJc4tTr6je4l2JF7+xXj/DvpXpJys44++NUOdS1LjfX5PC/rUtYqcgIsowj3n
> Xck7n77KaqRByUbs8lG/yGTYm1sY3fSwZUTt2XihmWPZQaOJaky/2CbEDGH8RNQ=
> =t71P
> -----END PGP SIGNATURE-----
>
>
Re: [DISCUSS] SVN to GIT for Airavata
Posted by Marlon Pierce <ma...@iu.edu>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'd really like to here from the GSOC students and others on the list
without SVN write access. Would you find things easier if you could
easily do a git fork?
Marlon
On 9/20/13 3:31 PM, Suresh Marru wrote:
> Hi All,
>
> One of the items we briefly listed on roadmap [1] is deciding on a SCM
which can go forward. Do we have any strong opinions on SVN Vs GIT? Just
starting a discussion.
>
> Suresh
> [1] - http://markmail.org/thread/5nq7jfk5b7izbip3
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJSPLG6AAoJEOEgD2XReDo5v1oH/RViy7qNDQgUmKcxlSM8Yi7d
f4DFRRG8JzP2QWotwUhkBGSYEPUgyVizg5JNzOxUGRFcTTRsz5GXV3ihursAM+6L
4OKJE9jTy3PMKOWjqdYRlpieDs3JbR9omc+Vkb1dOBkfgnS7xNBjPNxtlKheO+K3
OrjivVKgBdJCu+R3fSGmNfN0X1BGwfPEob8MeMV9prXaXKcl+1MuV175R+hB5eMO
dgBoJc4tTr6je4l2JF7+xXj/DvpXpJys44++NUOdS1LjfX5PC/rUtYqcgIsowj3n
Xck7n77KaqRByUbs8lG/yGTYm1sY3fSwZUTt2XihmWPZQaOJaky/2CbEDGH8RNQ=
=t71P
-----END PGP SIGNATURE-----
Re: [DISCUSS] SVN to GIT for Airavata
Posted by Danushka Menikkumbura <da...@gmail.com>.
A Big +1 for Git.
I think one of the major plus points in Git compared to Subversion is its
ability to merge branches more efficiently. Even cherry-picking comes in
very handy as it uses a global commit it across branches.
Other than that,
- It is less resource-hungry and faster. For instance creating a branch in
Git is just executing the branch command and checking it out in the current
working directory itself whereas in Subversion it ends up cloning the
current working directory into a new directory.
- A Git branch retains its entire history so that if you rename a file, you
can still see its entire history from its origin. I think this is a beauty.
- I also like Git's Web UI (repository browser) that has a very rich set of
features.
Danushka
On Sat, Sep 21, 2013 at 1:01 AM, Suresh Marru <sm...@apache.org> wrote:
> Hi All,
>
> One of the items we briefly listed on roadmap [1] is deciding on a SCM
> which can go forward. Do we have any strong opinions on SVN Vs GIT? Just
> starting a discussion.
>
> Suresh
> [1] - http://markmail.org/thread/5nq7jfk5b7izbip3
[DISCUSS] SVN to GIT for Airavata
Posted by Suresh Marru <sm...@apache.org>.
Hi All,
One of the items we briefly listed on roadmap [1] is deciding on a SCM which can go forward. Do we have any strong opinions on SVN Vs GIT? Just starting a discussion.
Suresh
[1] - http://markmail.org/thread/5nq7jfk5b7izbip3
Re: Roadmap to Airavata 1.0
Posted by Suresh Marru <sm...@apache.org>.
Good list Amila. I will start individual threads discussing each of the 1.0 aspects.
Suresh
On Aug 29, 2013, at 3:35 PM, Amila Jayasekara <th...@gmail.com> wrote:
>
> Hi Suresh,
>
> Some comments inline.
>
> Thanks
> Amila
>
> On Thu, Aug 29, 2013 at 9:39 AM, Suresh Marru <sm...@apache.org> wrote:
> Hi All,
>
> In the last 2 years Airavata has evolved significantly and I feel we are about the time to stabilize the Airavata Access Layer through a API and make a 1.0 release. Here are some thoughts on what we need to do before Airavata can be 1.0:
>
> * Ready to move into semantic versioning of releases
> * Have a API which will survive through minor releases and only calls out for API changes for major releases
> * Decide upon a going forward SCM among SVN or GIT
> * Have well documented client integration examples
> * Scrub of any unused dependencies and revisit the latest versions of critical dependencies
> * Agree upon supported features
> * Remove any third party maven repos (down to 1 as of today)
> * Resolve all the issues which are bugs (and preferably improvements as well)
> * Revisit all wish style issues and comment on the ones planned to be addressed in near future.
> * External review of the project by soliciting developers from fellow apache projects.
>
> Additional thoughts and tasks we need to accomplish before 1.0?
>
> Some more software engineering specific tasks
> 1. Improve test coverage - Specifically we need set of tests which actually execute workflows against stampede, trestles, lonestar etc ...
> 2. Clean up configurations
> 3. Resurrect Jenkins and do proper continuous integration
> 4. Reduce code duplication - I experienced some code duplications. E.g :- database connecting code (I my self also created one - my bad)
>
> Some questions
> - Are we going to include gsissh in 1.0 ?
> - Are we going to integrate Admin UI in 1.0 ? (which Vikness is doing)
> - Are we going to integrate XBaya Web UI 1.0 ? (which GSoc students are doing)
>
> Thanks
> Amila
>
>
> Suresh
>
Re: Roadmap to Airavata 1.0
Posted by Amila Jayasekara <th...@gmail.com>.
Hi Suresh,
Some comments inline.
Thanks
Amila
On Thu, Aug 29, 2013 at 9:39 AM, Suresh Marru <sm...@apache.org> wrote:
> Hi All,
>
> In the last 2 years Airavata has evolved significantly and I feel we are
> about the time to stabilize the Airavata Access Layer through a API and
> make a 1.0 release. Here are some thoughts on what we need to do before
> Airavata can be 1.0:
>
> * Ready to move into semantic versioning of releases
> * Have a API which will survive through minor releases and only calls out
> for API changes for major releases
> * Decide upon a going forward SCM among SVN or GIT
> * Have well documented client integration examples
> * Scrub of any unused dependencies and revisit the latest versions of
> critical dependencies
> * Agree upon supported features
> * Remove any third party maven repos (down to 1 as of today)
> * Resolve all the issues which are bugs (and preferably improvements as
> well)
> * Revisit all wish style issues and comment on the ones planned to be
> addressed in near future.
> * External review of the project by soliciting developers from fellow
> apache projects.
>
> Additional thoughts and tasks we need to accomplish before 1.0?
>
Some more software engineering specific tasks
1. Improve test coverage - Specifically we need set of tests which actually
execute workflows against stampede, trestles, lonestar etc ...
2. Clean up configurations
3. Resurrect Jenkins and do proper continuous integration
4. Reduce code duplication - I experienced some code duplications. E.g :-
database connecting code (I my self also created one - my bad)
Some questions
- Are we going to include gsissh in 1.0 ?
- Are we going to integrate Admin UI in 1.0 ? (which Vikness is doing)
- Are we going to integrate XBaya Web UI 1.0 ? (which GSoc students are
doing)
Thanks
Amila
> Suresh
Re: Roadmap to Airavata 1.0
Posted by Suresh Marru <sm...@apache.org>.
Hi All,
With GIT migration and thrift based Airavata API nicely shaping up, how about we target 1.0 release by Apache Con NA 2014?
I wanted to create a JIRA to track all pending tasks we listed, and co-incidentally noticed it marks the 1000th issue of Airavata :) https://issues.apache.org/jira/browse/AIRAVATA-1000
Suresh
On Nov 7, 2013, at 2:09 PM, Suresh Marru <sm...@apache.org> wrote:
> Looks like we are making good progress and there is lot of active development, but we will have to miss this deadline we set for ourselves. Instead of throwing another date, I will create a JIRA story and start linking major tasks so we can come up with a more informed timeline.
>
> Any objections to deferring the 1.0 release to some time early next year?
>
> Suresh
>
> On Aug 29, 2013, at 9:59 AM, Marlon Pierce <ma...@iu.edu> wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> I'm +1 for setting SC13 as a goal. It is a big opportunity since this
>> is when the e-science and cyberinfrastructure community will all be
>> together.
>>
>> But let's hear from everybody. Is Airavata 1.0 by SC13 achievable?
>>
>>
>> Marlon
>>
>>
>> On 8/29/13 9:49 AM, Suresh Marru wrote:
>>> On Aug 29, 2013, at 9:43 AM, Marlon Pierce <ma...@iu.edu>
>>> wrote:
>>>
>>> Looks like a good list. What is the time frame? SC13 and December
>>> 31 are two candidate dates to aim for.
>>>
>>>> I like both these dates. How about we target SC 13 [1] , i.e.
>>>> November 15th for a 1.0 release? and before end of year for
>>>> working with various users in upgrading to 1.0 version. That we
>>>> enter the new year, freshly returned from holidays with a target
>>>> for Airavata 2.0.
>>>
>>>> Suresh [1] - http://sc13.supercomputing.org/
>>>
>>>
>>>
>>> Marlon
>>>
>>>
>>> On 8/29/13 9:39 AM, Suresh Marru wrote:
>>>>>> Hi All,
>>>>>>
>>>>>> In the last 2 years Airavata has evolved significantly and I
>>>>>> feel we are about the time to stabilize the Airavata Access
>>>>>> Layer through a API and make a 1.0 release. Here are some
>>>>>> thoughts on what we need to do before Airavata can be 1.0:
>>>>>>
>>>>>> * Ready to move into semantic versioning of releases * Have a
>>>>>> API which will survive through minor releases and only calls
>>>>>> out for API changes for major releases * Decide upon a going
>>>>>> forward SCM among SVN or GIT * Have well documented client
>>>>>> integration examples * Scrub of any unused dependencies and
>>>>>> revisit the latest versions of critical dependencies * Agree
>>>>>> upon supported features * Remove any third party maven repos
>>>>>> (down to 1 as of today) * Resolve all the issues which are
>>>>>> bugs (and preferably improvements as well) * Revisit all wish
>>>>>> style issues and comment on the ones planned to be addressed
>>>>>> in near future. * External review of the project by
>>>>>> soliciting developers from fellow apache projects.
>>>>>>
>>>>>> Additional thoughts and tasks we need to accomplish before
>>>>>> 1.0?
>>>>>>
>>>>>> Suresh
>>>>>>
>>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
>> Comment: GPGTools - http://gpgtools.org
>> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>>
>> iQEcBAEBAgAGBQJSH1OwAAoJEOEgD2XReDo5uqgH/2HlGW1/i2ZQsC6a6SVmoqox
>> zcqwooLMwwDuaQvI1w3oZVFdcwNi5SBnRvazDwJY+iqvo1avxZ43EjBhSzrUk1hZ
>> zi6CntUG0wLS9sx8nbueoY05faV1+wJRJ5aRsyNfft6MOEdZQA0/rxM94hO5w71N
>> joqq6dZ2A1igmWKUB9WenGsIh96UV+pmO8wGFi9swy86DmczJcwyF8txpxmJxNIg
>> dwdTmFR6Gi8WQ2SZc3MHrMu8HByjwlKIH6Zv23R/TfVvieIenpd6tK6ZEuHH8ajI
>> D08T6AJKGsd4aR/KAU75rwo25hBFg1lA+wy8E7+N+pI5NdEz5Cx3dNkU4qI2Pw8=
>> =2KyM
>> -----END PGP SIGNATURE-----
>
Re: Roadmap to Airavata 1.0
Posted by Suresh Marru <sm...@apache.org>.
Looks like we are making good progress and there is lot of active development, but we will have to miss this deadline we set for ourselves. Instead of throwing another date, I will create a JIRA story and start linking major tasks so we can come up with a more informed timeline.
Any objections to deferring the 1.0 release to some time early next year?
Suresh
On Aug 29, 2013, at 9:59 AM, Marlon Pierce <ma...@iu.edu> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I'm +1 for setting SC13 as a goal. It is a big opportunity since this
> is when the e-science and cyberinfrastructure community will all be
> together.
>
> But let's hear from everybody. Is Airavata 1.0 by SC13 achievable?
>
>
> Marlon
>
>
> On 8/29/13 9:49 AM, Suresh Marru wrote:
>> On Aug 29, 2013, at 9:43 AM, Marlon Pierce <ma...@iu.edu>
>> wrote:
>>
>> Looks like a good list. What is the time frame? SC13 and December
>> 31 are two candidate dates to aim for.
>>
>>> I like both these dates. How about we target SC 13 [1] , i.e.
>>> November 15th for a 1.0 release? and before end of year for
>>> working with various users in upgrading to 1.0 version. That we
>>> enter the new year, freshly returned from holidays with a target
>>> for Airavata 2.0.
>>
>>> Suresh [1] - http://sc13.supercomputing.org/
>>
>>
>>
>> Marlon
>>
>>
>> On 8/29/13 9:39 AM, Suresh Marru wrote:
>>>>> Hi All,
>>>>>
>>>>> In the last 2 years Airavata has evolved significantly and I
>>>>> feel we are about the time to stabilize the Airavata Access
>>>>> Layer through a API and make a 1.0 release. Here are some
>>>>> thoughts on what we need to do before Airavata can be 1.0:
>>>>>
>>>>> * Ready to move into semantic versioning of releases * Have a
>>>>> API which will survive through minor releases and only calls
>>>>> out for API changes for major releases * Decide upon a going
>>>>> forward SCM among SVN or GIT * Have well documented client
>>>>> integration examples * Scrub of any unused dependencies and
>>>>> revisit the latest versions of critical dependencies * Agree
>>>>> upon supported features * Remove any third party maven repos
>>>>> (down to 1 as of today) * Resolve all the issues which are
>>>>> bugs (and preferably improvements as well) * Revisit all wish
>>>>> style issues and comment on the ones planned to be addressed
>>>>> in near future. * External review of the project by
>>>>> soliciting developers from fellow apache projects.
>>>>>
>>>>> Additional thoughts and tasks we need to accomplish before
>>>>> 1.0?
>>>>>
>>>>> Suresh
>>>>>
>>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQEcBAEBAgAGBQJSH1OwAAoJEOEgD2XReDo5uqgH/2HlGW1/i2ZQsC6a6SVmoqox
> zcqwooLMwwDuaQvI1w3oZVFdcwNi5SBnRvazDwJY+iqvo1avxZ43EjBhSzrUk1hZ
> zi6CntUG0wLS9sx8nbueoY05faV1+wJRJ5aRsyNfft6MOEdZQA0/rxM94hO5w71N
> joqq6dZ2A1igmWKUB9WenGsIh96UV+pmO8wGFi9swy86DmczJcwyF8txpxmJxNIg
> dwdTmFR6Gi8WQ2SZc3MHrMu8HByjwlKIH6Zv23R/TfVvieIenpd6tK6ZEuHH8ajI
> D08T6AJKGsd4aR/KAU75rwo25hBFg1lA+wy8E7+N+pI5NdEz5Cx3dNkU4qI2Pw8=
> =2KyM
> -----END PGP SIGNATURE-----
Re: Roadmap to Airavata 1.0
Posted by Marlon Pierce <ma...@iu.edu>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'm +1 for setting SC13 as a goal. It is a big opportunity since this
is when the e-science and cyberinfrastructure community will all be
together.
But let's hear from everybody. Is Airavata 1.0 by SC13 achievable?
Marlon
On 8/29/13 9:49 AM, Suresh Marru wrote:
> On Aug 29, 2013, at 9:43 AM, Marlon Pierce <ma...@iu.edu>
> wrote:
>
> Looks like a good list. What is the time frame? SC13 and December
> 31 are two candidate dates to aim for.
>
>> I like both these dates. How about we target SC 13 [1] , i.e.
>> November 15th for a 1.0 release? and before end of year for
>> working with various users in upgrading to 1.0 version. That we
>> enter the new year, freshly returned from holidays with a target
>> for Airavata 2.0.
>
>> Suresh [1] - http://sc13.supercomputing.org/
>
>
>
> Marlon
>
>
> On 8/29/13 9:39 AM, Suresh Marru wrote:
>>>> Hi All,
>>>>
>>>> In the last 2 years Airavata has evolved significantly and I
>>>> feel we are about the time to stabilize the Airavata Access
>>>> Layer through a API and make a 1.0 release. Here are some
>>>> thoughts on what we need to do before Airavata can be 1.0:
>>>>
>>>> * Ready to move into semantic versioning of releases * Have a
>>>> API which will survive through minor releases and only calls
>>>> out for API changes for major releases * Decide upon a going
>>>> forward SCM among SVN or GIT * Have well documented client
>>>> integration examples * Scrub of any unused dependencies and
>>>> revisit the latest versions of critical dependencies * Agree
>>>> upon supported features * Remove any third party maven repos
>>>> (down to 1 as of today) * Resolve all the issues which are
>>>> bugs (and preferably improvements as well) * Revisit all wish
>>>> style issues and comment on the ones planned to be addressed
>>>> in near future. * External review of the project by
>>>> soliciting developers from fellow apache projects.
>>>>
>>>> Additional thoughts and tasks we need to accomplish before
>>>> 1.0?
>>>>
>>>> Suresh
>>>>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJSH1OwAAoJEOEgD2XReDo5uqgH/2HlGW1/i2ZQsC6a6SVmoqox
zcqwooLMwwDuaQvI1w3oZVFdcwNi5SBnRvazDwJY+iqvo1avxZ43EjBhSzrUk1hZ
zi6CntUG0wLS9sx8nbueoY05faV1+wJRJ5aRsyNfft6MOEdZQA0/rxM94hO5w71N
joqq6dZ2A1igmWKUB9WenGsIh96UV+pmO8wGFi9swy86DmczJcwyF8txpxmJxNIg
dwdTmFR6Gi8WQ2SZc3MHrMu8HByjwlKIH6Zv23R/TfVvieIenpd6tK6ZEuHH8ajI
D08T6AJKGsd4aR/KAU75rwo25hBFg1lA+wy8E7+N+pI5NdEz5Cx3dNkU4qI2Pw8=
=2KyM
-----END PGP SIGNATURE-----
Re: Roadmap to Airavata 1.0
Posted by Suresh Marru <sm...@apache.org>.
On Aug 29, 2013, at 9:43 AM, Marlon Pierce <ma...@iu.edu> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Looks like a good list. What is the time frame? SC13 and December 31
> are two candidate dates to aim for.
I like both these dates. How about we target SC 13 [1] , i.e. November 15th for a 1.0 release? and before end of year for working with various users in upgrading to 1.0 version. That we enter the new year, freshly returned from holidays with a target for Airavata 2.0.
Suresh
[1] - http://sc13.supercomputing.org/
>
>
> Marlon
>
>
> On 8/29/13 9:39 AM, Suresh Marru wrote:
>> Hi All,
>>
>> In the last 2 years Airavata has evolved significantly and I feel
>> we are about the time to stabilize the Airavata Access Layer
>> through a API and make a 1.0 release. Here are some thoughts on
>> what we need to do before Airavata can be 1.0:
>>
>> * Ready to move into semantic versioning of releases * Have a API
>> which will survive through minor releases and only calls out for
>> API changes for major releases * Decide upon a going forward SCM
>> among SVN or GIT * Have well documented client integration
>> examples * Scrub of any unused dependencies and revisit the latest
>> versions of critical dependencies * Agree upon supported features *
>> Remove any third party maven repos (down to 1 as of today) *
>> Resolve all the issues which are bugs (and preferably improvements
>> as well) * Revisit all wish style issues and comment on the ones
>> planned to be addressed in near future. * External review of the
>> project by soliciting developers from fellow apache projects.
>>
>> Additional thoughts and tasks we need to accomplish before 1.0?
>>
>> Suresh
>>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQEcBAEBAgAGBQJSH1ASAAoJEOEgD2XReDo5h6sH/11h41zkjTyAT4BHo3IVaFe3
> IKB4Z4kZ5LSMnN6OJi/HVm2fEPf10rfFnNUdg3/8lgoWPvqlxkQiaDd0y5w3mfyk
> K/3yhF64Cp8lgirjWBsRvykOsn+U0anmEI8SvegVz6g2hXfwWIQ0D+4bCAOJgzkV
> 0B4SXWwBJYL8K/bbgZopWHvkV1aIvClN5wA2GviblgIuWUaD+b8BycTERipo6GJL
> 7RuUCSRnDOny3qw7Cqh0DMXlXtynjc4myiKo+UeBiq1eGTSQs1Pdf/D7fwKpz3SE
> XjqNtb8C4+8YigGT/v45w2lH1nERGtlJ6rKC5o8BqzMgYqbfe4tKWi2FpRMz9FA=
> =AeXF
> -----END PGP SIGNATURE-----
Re: Roadmap to Airavata 1.0
Posted by Marlon Pierce <ma...@iu.edu>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Looks like a good list. What is the time frame? SC13 and December 31
are two candidate dates to aim for.
Marlon
On 8/29/13 9:39 AM, Suresh Marru wrote:
> Hi All,
>
> In the last 2 years Airavata has evolved significantly and I feel
> we are about the time to stabilize the Airavata Access Layer
> through a API and make a 1.0 release. Here are some thoughts on
> what we need to do before Airavata can be 1.0:
>
> * Ready to move into semantic versioning of releases * Have a API
> which will survive through minor releases and only calls out for
> API changes for major releases * Decide upon a going forward SCM
> among SVN or GIT * Have well documented client integration
> examples * Scrub of any unused dependencies and revisit the latest
> versions of critical dependencies * Agree upon supported features *
> Remove any third party maven repos (down to 1 as of today) *
> Resolve all the issues which are bugs (and preferably improvements
> as well) * Revisit all wish style issues and comment on the ones
> planned to be addressed in near future. * External review of the
> project by soliciting developers from fellow apache projects.
>
> Additional thoughts and tasks we need to accomplish before 1.0?
>
> Suresh
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJSH1ASAAoJEOEgD2XReDo5h6sH/11h41zkjTyAT4BHo3IVaFe3
IKB4Z4kZ5LSMnN6OJi/HVm2fEPf10rfFnNUdg3/8lgoWPvqlxkQiaDd0y5w3mfyk
K/3yhF64Cp8lgirjWBsRvykOsn+U0anmEI8SvegVz6g2hXfwWIQ0D+4bCAOJgzkV
0B4SXWwBJYL8K/bbgZopWHvkV1aIvClN5wA2GviblgIuWUaD+b8BycTERipo6GJL
7RuUCSRnDOny3qw7Cqh0DMXlXtynjc4myiKo+UeBiq1eGTSQs1Pdf/D7fwKpz3SE
XjqNtb8C4+8YigGT/v45w2lH1nERGtlJ6rKC5o8BqzMgYqbfe4tKWi2FpRMz9FA=
=AeXF
-----END PGP SIGNATURE-----