09 Jan, 2018
3 commits
08 Jan, 2018
1 commit
06 Jan, 2018
1 commit
04 Jan, 2018
1 commit
01 Jan, 2018
1 commit
22 Dec, 2017
3 commits
21 Dec, 2017
3 commits
16 Oct, 2017
1 commit
10 Oct, 2017
1 commit
24 Sep, 2017
1 commit
18 Jul, 2017
1 commit
17 Jul, 2017
1 commit
-
It now tries to explicitly address evolution of our practices as the main goal of the article and describes with more words the problems faced on our situation.
07 Jul, 2017
1 commit
-
This requires a second pair of eyes. And the text quality is poor. This is more a draft than anything else.
05 Jul, 2017
1 commit
-
It needs to be reviewed by a second pair of eyes. Missing a review on similar work.
24 Jun, 2017
2 commits
-
Don't know if this is good.
-
The ICSE 2018 Software Engeneering in Practice Track page ( http://www.icse2018.org/track/icse-2018-Software-Engineering-in-Practice) specify the use of ACM's template. But do not specify which class to use. ACM's page specifies the following regarding this case: "Most proceedings authors (including ICPS authors) will use the "sigconf" proceedings template. If you are unsure which template variant to use, please request clarification from your event or publication contact." Thus until we get clarification on this matter I've set the template to sigcon. I've got the authors info from other articles in this repository. The section names and its presence/absence are not part of the template. I've just set a standard article format that we should modify as the article evolves.