--- !ditz.rubyforge.org,2008-03-06/issue 
title: document version compatibility expectations
desc: |-
  Most important is expectations for a maintained release (like 1.0), such as
  backporting of fixes (what kind?) and features (what kind?).
  
  API change compatibility: outline the basic expectation that APIs will either
  remain compatible or be removed entirely so that compile fails reliably.  Same
  for feature options.
type: :task
component: duk
release: v1.0
reporter: Sami Vaarala <sami.vaarala@iki.fi>
status: :closed
disposition: :fixed
creation_time: 2014-10-06 21:24:19.887598 Z
references: []

id: afdd37e32e5abfc07c1ff7bb8c8086c509847979
log_events: 
- - 2014-10-06 21:24:20.092617 Z
  - Sami Vaarala <sami.vaarala@iki.fi>
  - created
  - ""
- - 2014-10-07 19:31:31.513563 Z
  - Sami Vaarala <sami.vaarala@iki.fi>
  - changed status from unstarted to in_progress
  - ""
- - 2014-10-10 13:25:46.772143 Z
  - Sami Vaarala <sami.vaarala@iki.fi>
  - closed with disposition fixed
  - ""