Hi,
I think now it is time to discuss how we should proceed with the Sandbox
components and how we will release them.
The Sandbox is a place to develop components or tooling and to play with
new technologies around UIMA. If some of the components are stable and
tested they
should be included to a Sandbox release. A Sandbox release has the
advantage the users know what are the reliable components and what are the
components that are currently under development. I would like to release
the selected Sandbox components as bundle with each Apache UIMA release
under - "Apache UIMA Add-ons".
So the version number is the same for both releases and the effort is
minimized.
Advantages:
- release effort is minimized since only one release for all components
must be done
- you can download only one package that contains all the components and
tools
Disadvantages:
- the release number for a Sandbox component changes for each Apache
UIMA release independent of component changes
- the Sandbox components can not be downloaded separately which is maybe
an issue (??) for some companies
To do the release building I'm going to create a new Sandbox project
called "SandboxDistr" which contains all the information to build and
package the components.
For analysis engine components I have created a PEAR packager maven
plugin (plugin will also be added to the Sandbox) that will be used to
create a PEAR package automatically
during the build. My plan was to ship the PEAR package additionally in
the binary distribution for a component.
What do others think about this release approach?
Suggestions or comments?
-- Michael
