Thanks Milinda, it makes sense.

Hi Chris,

Thank you for the detailed response. Yes your suggestion of moving the 
0.2-incubating-SNAPSHOT to 0.2-incubating with a README addresses my concern. I 
will goahead and do that.

Suresh

On May 13, 2012, at 5:04 AM, Mattmann, Chris A (388J) wrote:

> Hey Suresh,
> 
> I'm never a fan of deleting anything and there are tons of archived emails 
> that reference this
> branch (e.g., list discussions, etc.)
> 
> Can't we just include a README.txt in the branch with your text below? Would 
> that suffice?
> I'd happily create it.
> 
> Looking at:
> 
> http://svn.apache.org/repos/asf/incubator/airavata/branches/
> 
> I assume we are talking here about:
> 
> http://svn.apache.org/repos/asf/incubator/airavata/branches/0.2-incubating-SNAPSHOT/
> 
> We should probably create an official 
> 
> http://svn.apache.org/repos/asf/incubator/airavata/branches/0.2-incubating/
> 
> that is an SVN copy of:
> 
> http://svn.apache.org/repos/asf/incubator/airavata/tags/0.2-incubating/
> 
> Let me know and thanks!
> 
> Cheers,
> Chris
> 
> On May 12, 2012, at 3:02 PM, Suresh Marru wrote:
> 
>> There is no active development on 0.2 branch and all changes to license and 
>> notice files are copied to trunk and we also have the release tag for 
>> reference for this code. Because of the delay in release, the branch is so 
>> far behind from the trunk.  Any objections to deleting 0.2-incubating branch 
>> to avoid any confusions?
>> 
>> Cheers,
>> Suresh
>> 
>> 
> 
> 
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattm...@nasa.gov
> WWW:   http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 

Reply via email to