Over the last few months the level of interest and activity in Merlin has been growing. In addition I have received several requests for a release of Merlin by people that want to get involved but really need a release before jumping in.
Some of the actions that should be taken before a release include the following:
|
Action
|
Status
|
|
custom contextualization tutorials
|
DONE
|
|
add documentation concerning the Merlin/Maven plugin
|
DONE
|
|
documentation on configuration/categories targets
|
DONE
|
|
provide solution for the a manifest generation problem that
is currently preventing the proper management of
extensions
|
DONE
|
|
enable meta-info generation tool to switch between xinfo
and xtype
|
DONE
|
|
document the repository and relationship to the classloader
and include resource tags
|
DONE
|
|
replace the attribute based lifestyle policy declaration with
a formal <lifestyle> element in the info block
|
DONE
|
|
replace the <engine> tag with <classloader>
|
DONE
|
|
documetation on logging categories management
(tutorials can come a little later)
|
DONE
|
|
Fork Excalibur Extension under the Merlin project.
|
DONE
|
|
dynamic components tutorials
|
DONE
|
|
complete the documentation about the James example
(this needs to cover the relationships between types, services,
packaged and explicit profiles, blocks, includes, and
targets).
|
PENDING
|
|
test and validation
|
ONGOING
|
|
tag the CVS
|
|
|
vote on a release
|
|
