[ome-users] [ome-devel] Image impoorters

[Ilya Goldberg]

Hi All
The new image importers in the IMPORT_CLEANUP_2006-06-27 branch were  
just merged with HEAD.
The OME code-base on CVS will most likely be tagged as the 2.6.0  
release candidate next week.
That means that no more features go into the 2.6.0 branch  
(OME_2_6_0), which is forevermore for bug fixing only.
Development will continue in CVS HEAD on OME 2.7.0

Please help us find bugs in 2.6.0 by checking out from CVS-HEAD until  
we announce the OME_2_6_0  branch.  Further testing should then take  
place on OME_2_6_0 until we release it officially.

Enjoy!
Ilya


On Jun 23, 2006, at 11:07 AM, Ilya Goldberg wrote:

> Hi All
> I know that some of you have developed your own flavors of image
> importers for getting images into OME.
> I have been working on some much needed cleaning up, bug fixing and
> optimizations in the import code (sub-classes of
> OME::ImportEngine::AbstractFormat), but unfortunately it will almost
> certainly break importers that are not in the code-base.
>
> Basically I wanted to take a little survey to find out how many
> custom importers are out there, and how this transition should be
> handled:
> A.  Commit new importers to CVS-HEAD and wait for the screaming.
> B.  Commit new importers to a branch for testing, then move to HEAD
> and wait for the screaming due to the ignored branch.
> C.  Volunteer to fix other people's importers for them.
>
> Probably everyone would prefer option C, but that all depends on how
> many of you are out there.
>
> -Ilya
>
> _______________________________________________
> ome-devel mailing list
> ome-devel at lists.openmicroscopy.org.uk
> http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel
>