Hi Gabriel, > > Personally I think people should need to explicitly subscribe to receive > > unstable/SNAPSHOT updates. > > I agree. But at the moment is it unclear what the "update" achieves.
The update mechanism allows you to upgrade to the latest release. Right now, that means upgrading from one beta to the another. There were issues upgrading from beta1, but e.g. a beta3 to beta4 upgrade will be possible using the updater. Later, once we have the unstable channel, we will have Jenkins publish the latest builds there. > In this page: > http://developer.imagej.net/development > > is this the latest/unstable?: > git clone git://github.com/imagej/imagej.git Yes, this gives you the entire Git repository. The master branch is the very latest code. Development is very active. You can browse the activity in a couple of places: http://trac.imagej.net/timeline (combined view of all branches) https://github.com/imagej/imagej/commits/master (activity on master branch) > 2.0.0-beta3 has a release date of July 13, > The zip with the "latest" snapshot has a date (the newest in the /jars folder) > of 12 of *June*, older than the beta3... Thank you for noticing this. The "Application build" link changed, but we forgot to update the web site to match. So it was a stale link from June 12. I have now fixed it to match the latest builds. Regards, Curtis On Sun, Aug 12, 2012 at 9:44 AM, Gabriel Landini <[email protected]>wrote: > On Monday 06 Aug 2012 20:16:04 Curtis Rueden wrote: > > > Personally I think people should need to explicitly subscribe to receive > > unstable/SNAPSHOT updates. > > I agree. But at the moment is it unclear what the "update" achieves. > There is little chance of being able to test any fixes if we cannot > download > these. I suppose that I could go the maven way and build some version, but > still not sure what > > In this page: > http://developer.imagej.net/development > > is this the latest/unstable?: > git clone git://github.com/imagej/imagej.git > > > Until we get the multiple channel updates working though, we are erring > on > > the side of caution with the update site, meaning you must explicitly > > download the latest snapshot build ZIP file if you want to try it before > > each beta release. > > Sure, but look at the dates of the files... > > 2.0.0-beta3 has a release date of July 13, > The zip with the "latest" snapshot has a date (the newest in the /jars > folder) > of 12 of *June*, older than the beta3... > > Cheers > > Gabriel > >
_______________________________________________ ImageJ-devel mailing list [email protected] http://imagej.net/mailman/listinfo/imagej-devel
