On Aug 9, 2011, at 10:48 , Marcus Denker wrote: > > Thanks! > >> >>> -> change the link >>> >>> http://www.pharo-project.org/pharo-download/unstable(-core) >>> to point to the one jenkins build of 1.4 >> >> I changed /unstable-core to point to >> https://ci.lille.inria.fr/pharo/view/Pharo%201.4/job/Pharo%201.4/lastSuccessfulBuild/artifact/Pharo-1.4.zip >> >> I assume there is no /unstable build (yet)? >> > For 1.4, we want to not have multiple images anymore... this is really > difficult to fix bugs in two images, it's hard to explain,
Right, that's what I remembered too (there fore the "yet" ;). My question was more regarding what we do with those links since there probably are scripts that use the /unstable-core and /unstable URLs. For now I made both point to .../lastSuccessfulBuild/artifact/Pharo-1.4.zip. >>> -> clean up a bit, no need to have pages for old .1 release. >> >> On pharo-project.org? >> > yes... the page for 1.1.1 we should merge into the page for 1.1 (just to make > it look cleaner) I would keep the old release pages for historic reasons, but move them out of the Download menu. We could add a page named "Previous releases" and link these pages from there. Then under "Download" in the menu, we only keep the most recent version. Adrian
