Really nice ideia. I got your point. I will test.
Thanks for the suggestion:)
Sent from Samsung tablet
Mensagem original
De : Patrick Dube
Data: 10/12/2015 18:26 (GMT-03:00)
Para: dev@cloudstack.apache.org
Assunto: Re: Feedback of my Phd work in Cloudstack Project
The history around the new file isn't the file itself, but in which
directory/package it would be in.
Cheers,
On Thu, Dec 10, 2015 at 3:01 PM, Igor Wiese wrote:
> Hi Patrick
>
> The problem with new files is the absence of history to build the
> prediction models. I need at least some commits (
Hi Patrick
The problem with new files is the absence of history to build the
prediction models. I need at least some commits (10 commits for example).
Yes, the link between files is what we are predicting. We can predict
changes involving commands.properties, XML files in general, .txt files, or
a
Are you handling new files as well, or the links between sets of files (or
packages)? As an example, if a user creates a new API cmd, then he will
update the "commands.properties" file. Another example, if a VO file is
updated, then there will be a db migration file added as well.
Cool work,
On Th
Hi Sebastien.
We used only 141 commits because we needed data from the issues. As my
assumption is related to the contextual information from Issues and Social
aspects, we need to aggregate commits and Issues.
First, I collected the issues from JIRA and then i tryed to aggregate the
commits that
On Dec 10, 2015, at 12:31 AM, Igor Wiese wrote:
> Hi, Cloudstack Community.
>
> My name is Igor Wiese, phd Student from Brazil. In my research, I am
> investigating two important questions: What makes two files change
> together? Can we predict when they are going to co-change again?
>
> I've
Hi Vadim!
In fact, we are recomending files to change together without the
developers/newcomer need to know about the code (structural dependencies
for example), or need to make debugging to find with files could change
together in a task.
We found many situations that files are changed together
Do I understand correctly that purpose of this work is to find tightly
coupled classes automatically in order to inverse dependency later on?
Vadim.
On 2015-12-10 01:31, Igor Wiese wrote:
Hi, Cloudstack Community.
My name is Igor Wiese, phd Student from Brazil. In my research, I am
investiga
Hi Anshul. Thanks for your answer
First of all, sorry about the webpage. I checked and now it is working
http://flosscoach.com/index.php/17-cochanges/67-cloudstack. Let me know if
you still having problem to access the webpage.
About your questions:
1) What do you mean by "correctly predict 60%
Before giving feedback I have some questions
1) What do you mean by "correctly predict 60% commits”?
2) What are the feature measures you are giving as input here to system
(prediction model)?
3) What kind of output you are expecting?
Web page link you have provided is not working.
> On 10-Dec-
Hi, Cloudstack Community.
My name is Igor Wiese, phd Student from Brazil. In my research, I am
investigating two important questions: What makes two files change
together? Can we predict when they are going to co-change again?
I've tried to investigate this question on the Cloudstack project. I'v
11 matches
Mail list logo
