Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airavata.apache.org
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Commit messages, Jira, and version control
From: Suresh Marru <smarru@apache.org>
In-Reply-To: 
 <CAKUcLKaaBZxbRvnEoMXqN17Fzpm0W2nTR-G6LcKG=-JXhU6T-Q@mail.gmail.com>
Date: Tue, 21 Jan 2014 21:49:42 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <D223264E-724F-4173-807A-7945EFD750AF@apache.org>
References: <52D83811.8000209@iu.edu>
 <44890635-B27E-48E0-876E-01F18E5BD42B@apache.org>
 <CAKUcLKZ5CCjbdJ5k6EKSn+uqhaN7=mHyPKvaOtvoYk4aLEcMwg@mail.gmail.com>
 <52DE89CD.1070904@iu.edu>
 <CAJvLytoOqY9B1LiP45U5mt0-y30LmxvYRvxk0tpqPk4jCyDd6w@mail.gmail.com>
 <52DECC51.3000605@iu.edu> <832A3FCC-AE37-4B72-83AB-CAAF875DD015@apache.org>
 <CAF4V=3HwqD8nmCsQBQwQ0sJ0X-D0oW6YdhRR6-mTTB=N3yyXgA@mail.gmail.com>
 <CAKUcLKaaBZxbRvnEoMXqN17Fzpm0W2nTR-G6LcKG=-JXhU6T-Q@mail.gmail.com>
To: Airavata Dev <dev@airavata.apache.org>

Actually I responded pre-maturely. I am myself not convinced if this =
will help or is needed. Let me withdraw my suggestion and stick to an =
opinion (for now) to have a single unified repo. We may want to once =
revisit the layout as we get close to 1.0.

Suresh

On Jan 21, 2014, at 9:46 PM, Amila Jayasekara <thejaka.amila@gmail.com> =
wrote:

> Hi Suresh,
>=20
> 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.=20
>=20
> Also Airavata is a fairly manageable code base. So I also dont see an =
advantage having separate repos for each of the sub-components.
>=20
> Thanks
> Amila
>=20
>=20
> On Tue, Jan 21, 2014 at 7:08 PM, Danushka Menikkumbura =
<danushka.menikkumbura@gmail.com> wrote:
> Suresh,
>=20
> IMO, having independent repositories does not really help unless the =
components are mutually exclusive and we ship them independently.
>=20
> Danushka
>=20
>=20
> On Wed, Jan 22, 2014 at 1:32 AM, Suresh Marru <smarru@apache.org> =
wrote:
> In retrospect, it may be better to make this decision now and have =
INFRA create the required repositories at once.
>=20
> I kind of liked what Shameera started, just to rephrase:
>=20
> * Airavata Services
> * Airavata Client SDK=92s
> * Airavata Web UI=92s
> * Airavata GUI Tools
> * Airavata Admin Tools
>=20
> I am + 0 on this. Not sure if breaking up will reduce clutter and =
provide better manageability or will overwhelm.
>=20
> Here are some examples, if it helps:
>=20
> https://github.com/jclouds
>=20
> And the master ASF repo which is an umbrella for all apache project =
mirrors - https://github.com/apache
>=20
> Suresh
>=20
>=20
> On Jan 21, 2014, at 2:36 PM, Marlon Pierce <marpierc@iu.edu> wrote:
>=20
> > For now, I want to keep the same structure with one repository. =
Assuming
> > 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? =
all
> >> Airavata code will go under one git repository or we will have =
separate
> >> 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.  Please vote only on the [VOTE] thread so =
that 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 <smarru@apache.org> =
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 =
has
> >>> 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 <marpierc@iu.edu> =
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 =
Jira
> >>>>>> 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 =
commit
> >>>>>> 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 =
if 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%2=
0text%20~%20%22git%20svn%22
> >>>>>
> >>>
> >>
> >
>=20
>=20
>=20