Installation in taskjuggler-0.0.11

- old
+ new

@@ -15,25 +15,49 @@
 Ruby applications are platform independent. There is no need to
 compile anything. But TaskJuggler has a very small set of
 dependencies that you have to take care of first. Please make sure you
 have the minimum required version installed.
 
+==== Supported Operating Systems ====
+
+* '''Linux''': Linux is the primary development platform for
+TaskJuggler. Releases are tested on recent openSUSE versions.
+
+* '''Other Unix OSes''': Should work as well, but releases are not
+tested on these OSes.
+
+* '''Windows''': Windows7 and some older version of Windows should
+work. There is no maintainer for this platform, so all releases are
+not tested on this platform.
+
+* '''MacOSX''': Will probably work as well. Releases are not tested
+on this OS. Older MacOS versions will likely not work.
+
+If you are interested in becoming the maintainer for any of the
+currently unmaintained (and untested) OSes, please contact us via the
+developer mailing list.
+
+==== Other required Software ====
+
 * '''Ruby:''' TaskJuggler III is written in Ruby.  You need a Ruby
 runtime environment to run it. This can be downloaded from
 [http://www.ruby-lang.org/en/downloads/ here].  Most Linux
 distributions usually have Ruby already included. So does MacOS X
 Leopard. For Windows, there is a one-click installer available. The
 recommended Ruby version to make full use of TaskJuggler is 1.9.2.
 Ruby 1.9.1 contains some bugs that prevent the multi-core support to
 work. For users that are not interested in multi-core support, the web
 server,  the time sheet infrastructure and daemon Ruby 1.8.7 is still
-ok to use.
+ok to use. On Windows you need at least Ruby 1.9.2.
 
 * '''RubyGems:''' If it did not come with your OS or the Ruby
 installation, see [http://docs.rubygems.org here] how to get and
 install it.
 
+Other versions of Ruby (Rubinius, JRuby, etc.) may work but have not
+been tested.
+
 === Installation Steps for Users ===
 
 ==== The easy way ====
 
 TaskJuggler is a commandline tool. It does not (yet) have a graphical
@@ -104,15 +128,14 @@
 
 Then checkout the source code with the following command
 
  git clone http://www.taskjuggler.org/git-repos/taskjuggler3.git
 
-Make sure, you
-have removed all previously installed instances of TaskJuggler from
-your system before doing so. It is a common mistake to have an old
-version of the TaskJuggler installed and then use parts of the old and
-new version together.
+Make sure, you have removed all previously installed instances of
+TaskJuggler from your system before doing so. It is a common mistake
+to have an old version of the TaskJuggler installed and then use parts
+of the old and new version together.
 
 If your Ruby installation does not come with the
 [http://rake.rubyforge.org Rake] build tool, you need to install it
 now.
 
@@ -148,6 +171,42 @@
 
   cd ${HOME}/bin
   ln -s tj3 tj3man
   ln -s tj3 tj3client
   ln -s tj3 tj3d
+
+=== Quickly switching between various TaskJuggler III versions ===
+
+One of the benefits of using TaskJuggler from the Git repository is
+the ability to get the latest bug fixes. If a bug was reported, it is
+usually fixed fairly quickly, but it can take several weeks before
+the next official release happens. The following commands must all be
+executed from within the checked-out Git directory.
+
+ git pull
+
+gets you the latest changes. We usually try to keep the head branch
+stable. Using it should not be much more risky than using a regular
+release. Nevertheless, problems can occur and a fixed version might
+take a few days.
+
+ git checkout -f XXXXXXXX
+
+will switch your current working copy to the version with commit ID
+XXXXXXXX. Alternatively, you can also use tag names.
+
+ git checkout -f release-0.0.10
+
+This will switch to the released version 0.0.10.
+
+ git tag
+
+provides you with a list of all tags.
+
+TaskJuggler III is written in Ruby. There is no make or build process
+needed. Every code change is effective immediately. The tutorial, the
+manual and some other parts do require a build step.
+
+ rake release
+
+will do it all and even create installable gem files again.
 