[ieeeSW] Drop future work sentences

Paulo Meireles
1 parent 5f1b08cd
Showing 1 changed file with 6 additions and 8 deletions Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
@@ -354,8 +354,7 @@ production in time.
  
 Due to the successful building of the CD pipeline, we improved the MP
 deployment process and kept the project alive. We map here lessons learned in
-this successful case, as well as issues that future works between industry and
-academia still need to address.
+this successful case.
  
 ### Build CD From Scratch
  
@@ -379,9 +378,7 @@ evolving the process on-the-fly.
 Building a CD pipeline was hard in the beginning. We believe that more tools to
 provide out-of-the-box standardized CD pipelines would be of great help for
 inexperienced teams. Tools that track each step of the pipeline and organize
-logs in a human-manageable way are necessary too. We also suggest further
-research on how to effectively spread knowledge across inexperienced developers
-in a high turnover scenario.
+logs in a human-manageable way are necessary too.
  
 ### Overcoming Mistrust
  
@@ -418,10 +415,11 @@ mobilization and responsiveness of our team to generate a new version package.
 On the other hand, technicians recognized the quality of our packages and our
 deployment process. Finally, the MP agents then realized that it could be
 beneficial for the project if they granted us access to the infrastructure,
-included the PE.
+including the PE.
  
-More research is required on developing protocols and policies to improve the
-relationship between industry and government, especially regarding CD.
+<!---
+Paulo: Acho que precisamos de algo ligado ao Ha-Ha-moment para fechar o texto aqui.
+-->
  
 ## Acknowledgements
...	...	@@ -354,8 +354,7 @@ production in time.
354	354
355	355	Due to the successful building of the CD pipeline, we improved the MP
356	356	deployment process and kept the project alive. We map here lessons learned in
357		-this successful case, as well as issues that future works between industry and
358		-academia still need to address.
	357	+this successful case.
359	358
360	359	### Build CD From Scratch
361	360
...	...	@@ -379,9 +378,7 @@ evolving the process on-the-fly.
379	378	Building a CD pipeline was hard in the beginning. We believe that more tools to
380	379	provide out-of-the-box standardized CD pipelines would be of great help for
381	380	inexperienced teams. Tools that track each step of the pipeline and organize
382		-logs in a human-manageable way are necessary too. We also suggest further
383		-research on how to effectively spread knowledge across inexperienced developers
384		-in a high turnover scenario.
	381	+logs in a human-manageable way are necessary too.
385	382
386	383	### Overcoming Mistrust
387	384
...	...	@@ -418,10 +415,11 @@ mobilization and responsiveness of our team to generate a new version package.
418	415	On the other hand, technicians recognized the quality of our packages and our
419	416	deployment process. Finally, the MP agents then realized that it could be
420	417	beneficial for the project if they granted us access to the infrastructure,
421		-included the PE.
	418	+including the PE.
422	419
423		-More research is required on developing protocols and policies to improve the
424		-relationship between industry and government, especially regarding CD.
	420	+<!---
	421	+Paulo: Acho que precisamos de algo ligado ao Ha-Ha-moment para fechar o texto aqui.
	422	+-->
425	423
426	424	## Acknowledgements
427	425
...	...