Return-Path: X-Original-To: apmail-airavata-dev-archive@www.apache.org Delivered-To: apmail-airavata-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 72B3C10216 for ; Wed, 22 Jan 2014 02:47:01 +0000 (UTC) Received: (qmail 95383 invoked by uid 500); 22 Jan 2014 02:47:00 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 95257 invoked by uid 500); 22 Jan 2014 02:46:56 -0000 Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airavata.apache.org Delivered-To: mailing list dev@airavata.apache.org Received: (qmail 95249 invoked by uid 99); 22 Jan 2014 02:46:56 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Jan 2014 02:46:56 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of thejaka.amila@gmail.com designates 209.85.219.52 as permitted sender) Received: from [209.85.219.52] (HELO mail-oa0-f52.google.com) (209.85.219.52) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Jan 2014 02:46:52 +0000 Received: by mail-oa0-f52.google.com with SMTP id i4so3560473oah.39 for ; Tue, 21 Jan 2014 18:46:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=AzMtowivFSiIa8U0p7UKRxjuR0CbPBjN5V7uzurF3C8=; b=0zs2zMk9vvMmpbbONm8dYwaAWbMaGGY4JVIBL5LZvO+RHYLtKpQo2FJC73avm5X0H1 9VqxG6uC02nlSfBUKF4vRpt9LkXTq9eDu6GOiiPInKRKs8mRrOyduvDaODGssY+rLRel UMyEz8029dhWALMGYKE71SNAq9aqLQlOtcToLIxIqSMlscV31wll6N/LqQJVCaEk8VNL vw27gfmmcKVRU2sq2JDneMbULiUZM+AYI2lBQtgtJxPUq5pWlu4thTBJ8rmUvFDEwHyR XpI47ul4OJ1+lARuHDYMqY1jONu8gdV2iTaZnN2daA3kcozED6vabhp55oMOOQV7Frat rJOA== MIME-Version: 1.0 X-Received: by 10.182.158.71 with SMTP id ws7mr24206587obb.6.1390358791171; Tue, 21 Jan 2014 18:46:31 -0800 (PST) Received: by 10.76.169.136 with HTTP; Tue, 21 Jan 2014 18:46:31 -0800 (PST) In-Reply-To: References: <52D83811.8000209@iu.edu> <44890635-B27E-48E0-876E-01F18E5BD42B@apache.org> <52DE89CD.1070904@iu.edu> <52DECC51.3000605@iu.edu> <832A3FCC-AE37-4B72-83AB-CAAF875DD015@apache.org> Date: Tue, 21 Jan 2014 21:46:31 -0500 Message-ID: Subject: Re: Commit messages, Jira, and version control From: Amila Jayasekara To: dev Content-Type: multipart/alternative; boundary=089e01494a16dbb6a004f08621d0 X-Virus-Checked: Checked by ClamAV on apache.org --089e01494a16dbb6a004f08621d0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Suresh, I didnt quite understand what you proposed. Are you proposing to have separate repos for "Airavata Services", "Airavata Client SDK=92s" etc ... ? If so I am with Danushka. Also Airavata is a fairly manageable code base. So I also dont see an advantage having separate repos for each of the sub-components. Thanks Amila On Tue, Jan 21, 2014 at 7:08 PM, Danushka Menikkumbura < danushka.menikkumbura@gmail.com> wrote: > Suresh, > > IMO, having independent repositories does not really help unless the > components are mutually exclusive and we ship them independently. > > Danushka > > > On Wed, Jan 22, 2014 at 1:32 AM, Suresh Marru wrote: > >> In retrospect, it may be better to make this decision now and have INFRA >> create the required repositories at once. >> >> I kind of liked what Shameera started, just to rephrase: >> >> * Airavata Services >> * Airavata Client SDK=92s >> * Airavata Web UI=92s >> * Airavata GUI Tools >> * Airavata Admin Tools >> >> I am + 0 on this. Not sure if breaking up will reduce clutter and provid= e >> better manageability or will overwhelm. >> >> Here are some examples, if it helps: >> >> https://github.com/jclouds >> >> And the master ASF repo which is an umbrella for all apache project >> mirrors - https://github.com/apache >> >> Suresh >> >> >> On Jan 21, 2014, at 2:36 PM, Marlon Pierce wrote: >> >> > For now, I want to keep the same structure with one repository. Assumi= ng >> > the vote passes, this will be a simple email to Apache INFRA to do the >> > conversion. We can bring up reorganization separately. >> > >> > Please let me know if I am missing something, though. >> > >> > >> > Marlon >> > >> > On 1/21/14 2:28 PM, Shameera Rathnayaka wrote: >> >> Hi Marlon, >> >> >> >> do we have any idea about the git repository structure we will use? a= ll >> >> Airavata code will go under one git repository or we will have separa= te >> >> repository to airavata client , airvata server and xBaya? (can be fin= e >> >> grain further if needed). >> >> >> >> Thanks, >> >> Shameera. >> >> >> >> >> >> On Tue, Jan 21, 2014 at 8:23 PM, Marlon Pierce >> wrote: >> >> >> >>> Since this will effect everyone, I will start a 72 hour voting perio= d >> >>> and discussion thread. Please vote only on the [VOTE] thread so tha= t >> it >> >>> will be easy to count. All opinions are welcome. >> >>> >> >>> >> >>> Marlon >> >>> >> >>> On 1/16/14 10:51 PM, Amila Jayasekara wrote: >> >>>> +1 to move to Git. >> >>>> It seems it is easy for people to contribute with GIT. (Specially >> >>>> situations like GSOC). >> >>>> >> >>>> Thanks >> >>>> Thejaka Amila >> >>>> >> >>>> >> >>>> On Thu, Jan 16, 2014 at 4:54 PM, Suresh Marru >> wrote: >> >>>> >> >>>>> Thanks Marlon for resurrecting this discussion. Its also timely to >> the >> >>>>> transition before GSOC 14 and as we move towards Airavata 1.0. >> >>>>> >> >>>>> One thing we have noticed is INFRA support for GIT transition has >> >>>>> increased over time. Also, the integration with GITHUB, jClouds ha= s >> >>> fully >> >>>>> exploited this and now there may be other projects also. So all in >> all >> >>> the >> >>>>> timing is very good and + 1 to move foreword for Airavata. >> >>>>> >> >>>>> Suresh >> >>>>> >> >>>>> On Jan 16, 2014, at 2:50 PM, Marlon Pierce wrote= : >> >>>>> >> >>>>>> Hi all-- >> >>>>>> >> >>>>>> We have discussed $subject before for other reasons without much >> action >> >>>>>> [0], so I want to bring it up again. Unless the situation has >> changed >> >>>>>> recently, Apache's Jira no longer links SVN commit messages to Ji= ra >> >>>>>> tickets. For background on the issues with SVN, see [1]. This >> ticket >> >>>>>> is still unresolved. >> >>>>>> >> >>>>>> The general linking of repo commits to Jira tickets through commi= t >> >>>>>> comments [2] is a good and virtuous thing. We have lost this in >> >>>>>> Airavata and need to get it back. This requires moving to Git [3= ] >> [4]. >> >>>>>> >> >>>>>> What other consequences are there for doing this? Let's please >> >>>>>> discuss. It will take a bit of time from INFRA to make the >> conversion, >> >>>>>> but this doesn't seem to be awful. We need to preserve history i= f >> we >> >>> do >> >>>>>> this. What else? >> >>>>>> >> >>>>>> >> >>>>>> Thanks-- >> >>>>>> >> >>>>>> >> >>>>>> Marlon >> >>>>>> >> >>>>>> [0] >> https://www.mail-archive.com/dev@airavata.apache.org/msg03881.html >> >>>>>> >> >>>>>> [1] https://ecosystem.atlassian.net/browse/SVN-385 >> >>>>>> >> >>>>>> [2] http://www.apache.org/dev/svngit2jira.html >> >>>>>> >> >>>>>> [3] https://git-wip-us.apache.org/ >> >>>>>> >> >>>>>> [4] >> >>>>>> >> >>> >> https://issues.apache.org/jira/issues/?jql=3Dproject%20%3D%20INFRA%20AND= %20text%20~%20%22git%20svn%22 >> >>>>> >> >>> >> >> >> > >> >> > --089e01494a16dbb6a004f08621d0 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable
Hi Suresh,

I didnt quite understand wha= t you proposed. Are you proposing to have separate repos for "Airavat= a Services", "Airavata Client SDK=92s" etc ... ?
If so I am with Danushka.=A0

= Also Airavata is a fairly=A0manageable=A0c= ode base. So I also dont see an advantage having separate repos for each of= the sub-components.

Thanks
Amila


On Tue,= Jan 21, 2014 at 7:08 PM, Danushka Menikkumbura <danushka.me= nikkumbura@gmail.com> wrote:
Suresh,

= IMO, having independent repositories does not really help unless the compon= ents are mutually exclusive and we ship them independently.

Danushka=


On Wed, Jan 2= 2, 2014 at 1:32 AM, Suresh Marru <smarru@apache.org> wrote:<= br>
In retrospect, it may be better to make this decision now and have INFRA cr= eate the required repositories at once.

I kind of liked what Shameera started, just to rephrase:

* Airavata Services
* Airavata Client SDK=92s
* Airavata Web UI=92s
* Airavata GUI Tools
* Airavata Admin Tools

I am + 0 on this. Not sure if breaking up will reduce clutter and provide b= etter manageability or will overwhelm.

Here are some examples, if it helps:

https://github.com= /jclouds

And the master ASF repo which is an umbrella for all apache project mirrors= - https://github.c= om/apache

Suresh


On Jan 21, 2014, at 2:36 PM, Marlon Pierce <marpierc@iu.edu> wrote:

> For now, I want to keep the same structure with one repository. Assumi= ng
> the vote passes, this will be a simple email to Apache INFRA to do the=
> conversion. =A0We can bring up reorganization separately.
>
> Please let me know if I am missing something, though.
>
>
> Marlon
>
> On 1/21/14 2:28 PM, Shameera Rathnayaka wrote:
>> Hi Marlon,
>>
>> do we have any idea about the git repository structure we will use= ? all
>> Airavata code will go under one git repository or we will have sep= arate
>> repository to airavata client , airvata server and xBaya? (can be = fine
>> grain further if needed).
>>
>> Thanks,
>> Shameera.
>>
>>
>> On Tue, Jan 21, 2014 at 8:23 PM, Marlon Pierce <marpierc@iu.edu> wrote:
>>
>>> Since this will effect everyone, I will start a 72 hour voting= period
>>> and discussion thread. =A0Please vote only on the [VOTE] threa= d so that it
>>> will be easy to count. =A0All opinions are welcome.
>>>
>>>
>>> Marlon
>>>
>>> On 1/16/14 10:51 PM, Amila Jayasekara wrote:
>>>> +1 to move to Git.
>>>> It seems it is easy for people to contribute with GIT. (Sp= ecially
>>>> situations like GSOC).
>>>>
>>>> Thanks
>>>> Thejaka Amila
>>>>
>>>>
>>>> On Thu, Jan 16, 2014 at 4:54 PM, Suresh Marru <smarru@apache.org> w= rote:
>>>>
>>>>> Thanks Marlon for resurrecting this discussion. Its al= so timely to the
>>>>> transition before GSOC 14 and as we move towards Airav= ata 1.0.
>>>>>
>>>>> One thing we have noticed is INFRA support for GIT tra= nsition has
>>>>> increased over time. Also, the integration with GITHUB= , jClouds has
>>> fully
>>>>> exploited this and now there may be other projects als= o. So all in all
>>> the
>>>>> timing is very good and + 1 to move foreword for Airav= ata.
>>>>>
>>>>> Suresh
>>>>>
>>>>> On Jan 16, 2014, at 2:50 PM, Marlon Pierce <marpierc@iu.edu> wrote= :
>>>>>
>>>>>> Hi all--
>>>>>>
>>>>>> We have discussed $subject before for other reason= s without much action
>>>>>> [0], so I want to bring it up again. =A0Unless the= situation has changed
>>>>>> recently, Apache's Jira no longer links SVN co= mmit messages to Jira
>>>>>> tickets. =A0For background on the issues with SVN,= see [1]. =A0This ticket
>>>>>> is still unresolved.
>>>>>>
>>>>>> The general linking of repo commits to Jira ticket= s through commit
>>>>>> comments [2] is a good and virtuous thing. =A0We h= ave lost this in
>>>>>> Airavata and need to get it back. =A0This requires= moving to Git [3] [4].
>>>>>>
>>>>>> What other consequences are there for doing this? = =A0Let's please
>>>>>> discuss. =A0It will take a bit of time from INFRA = to make the conversion,
>>>>>> but this doesn't seem to be awful. =A0We need = to preserve history if we
>>> do
>>>>>> this. =A0What else?
>>>>>>
>>>>>>
>>>>>> Thanks--
>>>>>>
>>>>>>
>>>>>> Marlon
>>>>>>
>>>>>> [0] https://www.mail-archive= .com/dev@airavata.apache.org/msg03881.html
>>>>>>
>>>>>> [1] https://ecosystem.atlassian.net/browse/SVN-3= 85
>>>>>>
>>>>>> [2] http://www.apache.org/dev/svngit2jira.html >>>>>>
>>>>>> [3] https://git-wip-us.apache.org/
>>>>>>
>>>>>> [4]
>>>>>>
>>> https= ://issues.apache.org/jira/issues/?jql=3Dproject%20%3D%20INFRA%20AND%20text%= 20~%20%22git%20svn%22
>>>>>
>>>
>>
>



--089e01494a16dbb6a004f08621d0--