Release preparations

* README: New link to README.md, to make automake --gnu happe.
* configure.ac: Bump version in anticipation of release.
* fibers.texi: Start to flesh out a bit more.

README

@@ -0,0 +1 @@
+README.md

configure.ac

@@ -19,7 +19,7 @@ License along with this program.  If not, see
 ]])
 
 AC_PREREQ(2.52)
-AC_INIT([fibers], [0.1.0])
+AC_INIT([fibers], [0.2.0])
 AC_CONFIG_SRCDIR([env.in])
 AC_CONFIG_AUX_DIR([build-aux])
 AC_CONFIG_MACRO_DIRS([m4])

fibers.texi

@@ -44,7 +44,9 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
 
 @insertcopying
 @menu
-* Introduction::                     What's this all about?
+* Introduction::          What's this all about?
+* Reference::             API reference.
+* Status::                Fibers is a work in progress.
 @end menu
 
 @end ifnottex
@@ -58,6 +60,12 @@ Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
 
 Fibers is a facility for lightweight concurrency in Guile.
 
+@menu
+* Context::               How do other systems handle concurrency?
+* Design::                Fibers' point in the design space.
+@end menu
+
+@node Context
 @section A brief history of language facilities for concurrency
 
 Modern machines have the raw capability to serve hundreds of thousands
@@ -208,6 +216,7 @@ primitive to synchronize on one of a number of events, Concurrent ML
 allows programs to build @code{select} in user-space.  It looks like
 the right direction for Guile to go too.
 
+@node Design
 @section Fibers design
 
 In Fibers, the unit of computation is the @dfn{fiber}, a lightweight
@@ -289,6 +298,13 @@ scheduler, instate it on the thread, add some fibers, then run the
 scheduler.  That call to run the scheduler will only return when there
 there are no more fibers waiting to be scheduled.
 
+@node Reference
+@chapter API reference
+
+@node Status
+@chapter Project status
+
+
 @c @node Concept Index
 @c @unnumbered Concept Index
 @c @printindex cp