Difference between revisions of "Continuous rewriting"

From CitconWiki
Jump to navigationJump to search
(Plea for contributions to the Continuous rewriting page.)
 
(first draft of chart)
Line 1: Line 1:
To those who were in this session, I heard many positive things about it, please can you write some notes here?
+
Squirrel presented for discussion the thesis that "Continuous Rewriting" is an emerging theme for software development, a successor to better-known ideas "Continuous Integration" and "Continuous Deployment". The session opened with discussion of this chart:
  
Thanks
+
{| class="wikitable"
 
+
|-
 
+
! scope="col"|
Julian who was part of another session at the time...
+
! scope="col"| 2000-3
 +
! scope="col"| 2004-6
 +
! scope="col"| 2007-9
 +
! scope="col"| 2010-12
 +
! scope="col"| 2012-
 +
|-
 +
! scope="row"| Continuous Integration
 +
| ''Integration hurts, so automate & do more often.'' - Daily Builds, Ant, CruiseControl
 +
| More tools! - JetBrains, Hudson, BuildForge
 +
| Adopted by advanced teams - CI books, CITCON
 +
| Tool shakeout, standard for new teams - Jenkins
 +
| Adopted by late majority?
 +
|-
 +
! scope="row"| Continuous Deployment
 +
| foo
 +
| foo
 +
| foo
 +
| foo
 +
| foo
 +
|-
 +
! scope="row" | Continuous Rewriting
 +
| foo
 +
| foo
 +
| foo
 +
| foo
 +
| foo
 +
|}

Revision as of 13:49, 8 November 2012

Squirrel presented for discussion the thesis that "Continuous Rewriting" is an emerging theme for software development, a successor to better-known ideas "Continuous Integration" and "Continuous Deployment". The session opened with discussion of this chart:

2000-3 2004-6 2007-9 2010-12 2012-
Continuous Integration Integration hurts, so automate & do more often. - Daily Builds, Ant, CruiseControl More tools! - JetBrains, Hudson, BuildForge Adopted by advanced teams - CI books, CITCON Tool shakeout, standard for new teams - Jenkins Adopted by late majority?
Continuous Deployment foo foo foo foo foo
Continuous Rewriting foo foo foo foo foo