Contents

Introduction:
To see the latest list of the change log please visit the Change Log page at www.majoron.com.

Legend:
Follow notation is used at change log, roadmap and known bugs. Each bug begins with a version,
then follow category of the bug inside {}. It can be bug report, feature request and etc.
Then follow component inside []. After follow bug number at bug tracking system between // signs.
And then follow a short description of the bug.

Example:
For example bug: "1.0 { Feature Request } [ AntHill ] / 380 / STLport support required" means
that bug was created for 1.0 version of the AntHill component, bug is feature request with
380 number at bug tracking system. And bug requires STLPort support implementation.

 Version 0.2
 -----------
0.2 { Bug Report } [ Clockworkd ] / X / Add before_fork & after fork hook to restore ActiveRecord connection after fork
0.2 { Bug Report } [ Clockworkd ] / X / Support rails 2.5.x
0.2 { Bug Report } [ Clockworkd ] / X / Generator that install clockwork to script was added
0.2 { Bug Report } [ Clockworkd ] / X / Capistrano receips was added
0.2 { Bug Report } [ Clockworkd ] / X / Monit script was added
0.2 { Bug Report } [ Clockworkd ] / X / Ability to run as daemons was added

Version data entries

1 entries across 1 versions & 1 rubygems

Version	Path
clockworkd-0.2.5	changelog