Posted by
dscho on
May 31, 2013; 2:48pm
URL: http://imagej.273.s1.nabble.com/ImageJ-release-cycle-tp5003165p5003174.html
Hi José María,
On Fri, 31 May 2013, José María Mateos wrote:
> Just a quick question: why ImageJ version 1.47 cannot be downloaded
> directly from the download page and has to be obtained as an update for
> the 1.46 version?
As Michael pointed out, release management is a major task.
Having said that, the Fiji distribution of ImageJ makes this much easier
by having update sites which keep the distribution up-to-date; developers
upload new versions, and user installations suggest upgrading
automatically.
This system allows us to keep ImageJ up-to-date painlessly; it always
ships with the current minor version (at the time of writing, ImageJ
1.47q).
This system also allows us to offer Fiji as a continuous release, i.e. the
packages are updated automatically whenever something new -- including new
ImageJ versions -- is uploaded to the Fiji update site; this avoids to
require users to know implementation details such as: which command to
execute to update to the latest version, what files are required, where
they need to be put, etc
The whole point of the Fiji distribution of ImageJ is convenience.
Wayne, I would be very happy to contribute my experience and knowledge
about the continuous release management to install a new job on our
continuous integration server to create ImageJ packages for every new
minor version and and for all "nightly builds" automatically.
Please tell me if you're interested!
Ciao,
Johannes
--
ImageJ mailing list:
http://imagej.nih.gov/ij/list.html