Posted by
ctrueden on
Aug 14, 2014; 9:27pm
URL: http://imagej.273.s1.nabble.com/SCIFIO-Unusable-tp5009195p5009221.html
Hi Michael,
> Is there any plan to have a 'stable' branch of ImageJ2, from which
> ordinary users can update with some degree of certainty that stuff
> won't break, and a beta branch for those who like to try the new stuff
> which might break, and a dev branch for the devs and bug testers,
> where stuff really is half-broken/half-built most of the time?
Some components of ImageJ2 and Fiji have indeed migrated to such a model.
The stable release of Bio-Formats ships with Fiji, with development
versions available from the "Bio-Formats" update site. The situation is
similar for TrackMate and SCIFIO, which have the TrackMate-dev and
SCIFIO-dev update sites, respectively. It seems likely that this trend will
continue.
Regards,
Curtis
On Thu, Aug 14, 2014 at 11:48 AM, Doube, Michael <
[hidden email]> wrote:
> Dear ImageJ/Fiji-ers
>
> > is a beta product and right now it's a step backwards
> > from classic ImageJ functionality. We enabled it by default
>
> How is it a coherent strategy to enable beta functionality by default, and
> foist it upon end users?
>
> Is there any plan to have a 'stable' branch of ImageJ2, from which
> ordinary users can update with some degree of certainty that stuff won't
> break, and a beta branch for those who like to try the new stuff which
> might break, and a dev branch for the devs and bug testers, where stuff
> really is half-broken/half-built most of the time? I realise that IJ2 is
> still in relatively unstable release-candidate times, but it would be nice
> to know what future plans may be.
>
> My single biggest concern about Fiji is that updates break stuff for users
> far too often. Sometimes the screams of pain and frustration make it to the
> mailing list, but I suspect that often they disappear, unheard, in the dark
> corners of imaging labs around the world. I really hope that as ImageJ2
> matures, it adopts a conservative approach to updating userland
> installations - i.e. only sending stuff to the updater once it's pretty
> well hardened.
>
> Michael
>
>
>
>
> <
http://www.rvc.ac.uk>
>
> This message, together with any attachments, is intended for the stated
> addressee(s) only and may contain privileged or confidential information.
> Any views or opinions presented are solely those of the author and do not
> necessarily represent those of the Royal Veterinary College.
>
> --
> ImageJ mailing list:
http://imagej.nih.gov/ij/list.html>
--
ImageJ mailing list:
http://imagej.nih.gov/ij/list.html