--- !ditz.rubyforge.org,2008-03-06/issue 
title: separate website to its own repo
desc: |-
  There are some dependencies to break first in buildsite.py:
  
  * scrapes duktape.h to get version number
  
  * needs the examples/guide and examples/hello directories for reading
  
  * needs RELEASES.txt
  
  * needs dukweb.js, jquery, and dukweb support files for REPL page
  
  Most (all?) of these can be fixed by cloning the Duktape repo when building
  the website.
  
  Separating the repos also prevents generated HTML documentation from being
  included in the Duktape distributable.  This is perhaps most easily fixed
  by making the duktape repo build a plain distributable, and then add the
  HTML documentation into the final distributable through the website build
  scripts.  In effect, the final distributable would actually be built by the
  duktape website repo scripts.
type: :task
component: duk
release: 
reporter: sva <sami.vaarala@iki.fi>
status: :unstarted
disposition: 
creation_time: 2014-03-10 15:38:16.358062 Z
references: []

id: bb5d9378c73e45df5421c0bd9e458e35c0c69120
log_events: 
- - 2014-03-10 15:38:16.517608 Z
  - sva <sami.vaarala@iki.fi>
  - created
  - ""
- - 2014-03-28 10:26:28.163762 Z
  - Sami Vaarala <sami.vaarala@iki.fi>
  - assigned to release v0.11 from v0.10
  - ""
- - 2014-04-30 12:41:08.885242 Z
  - Sami Vaarala <sami.vaarala@iki.fi>
  - unassigned from release v0.11
  - ""