Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [gemoc-dev] [GEMOC] Moving older releases and milstones to archive.eclipse.org

note: I answer on the dev list only (and do not continue the thread on all@xxxxxxxxx)

done for the 5 currently moved milestone (3.0.0-rc1..rc4 and 3.1.0-20190627) with Erwan redirection suggestion. 

for other commiters:  move and redirection creation is done via jobs scripts on the ci.eclipse.gemoc.  I'll put a reminder note in the wiki https://github.com/eclipse/gemoc-studio/wiki/Official-commiter-memo
 

However I think there are some cases were the redirection will not help, such as direct link to a specific artifact or a specific documentaton page.
Similarly, using link to the updatesite sites will not work too.  (the user will have to try in a browser, and see that she's been redirected to a new url)

All the best
Didier

Le 17/12/2019 à 11:58, Erwan Bousse a écrit :

Le mar., déc. 17, 2019 at 11:39, Didier Vojtisek <didier.vojtisek@xxxxxxxx> a écrit :
Hi Benoit

The choice comes from eclipse were projects are encourage to keep a "reasonable" amount of data on download.eclipse.org and move older content to archive (several projects including GEMOC were pointed out in a recent message) This is  because download.eclipse.org is mirrored across the world (which speed up the download when using the correct url but with a increased impact for all servers)

You're right that this is very tough but we cannot keep the artifacts indefinitely on this server.

For this new milestone I already put the artifacts on both download and archive, thus the links using archive.eclipse.org will be long term. (similar to url pointing to the release notes on gemoc.org website). So I plan to do the same for future milestones and releases too.

In complement, for moved artifacts, I plan to put in the original folder a web page indicating the new location.


Why not puting  "index.html" files with redirections in all folders of download.eclipse.org? Something like this in each file :

<meta http-equiv="refresh" content="0; url="" href="http://archive.eclipse.org/" class="" moz-do-not-send="true">archive.eclipse.org/…" />





Last, the "keep last milestone and last release" rule is not that strict, we can probably afford to keep the artifacts a little bit longer (the three last  should be acceptable in term of disk space on mirror server)

I'll add a footnote in the release note, inviting paper/tutorial authors to use either the release note url or the archive url  as permalinks and not the download.eclipse.org urls

All the best
Didier

Le 16/12/2019 à 21:48, Benoit Combemale a écrit :
Dear Didier, 

The choice (imposed by Eclipse?) to only have a short term URL for the latest milestone is very tough and damaging. The usual scenario is to initially communicate on the latest milestone (yes, we are proud of the latest feature, and happy to communicate on it), and then this communication remains over the time. However, the latest milestone become eventually the non latest, meaning now the URL is not anymore valid. 

In conclusion, it’s not anymore possible to communicate (i.e. archival materials such as slides, articles, tutorials, etc.) on the latest milestone… 

I do not think this can be acceptable, and need a deeper discussion on the topics, such as we can have sustainable URLs (why not putting directly on archive.eclipse.org? Or to manage redirect? Or?). In the meantime, this imposes us to only communicate about <gemoc.org/studio + version> to keep sustainable the information we provide. 

All the best, 
benoit

--
Benoit Combemale
Professor, Univ. Toulouse & Inria
https://www.irit.fr/~Benoit.Combemale

Le 16 déc. 2019 à 14:54, Didier Vojtisek <didier.vojtisek@xxxxxxxx> a écrit :

Hi

As asked by Eclipse webmasters, we're moving our older milestones and releases to archive.eclipse.org instead of download.eclipse.org  (in order to decrease the overhead on the mirror servers)

We will keep on the main download server only the latest milestone, the latest release, and the latest nightly build.

Obviously, we'll update the links on the release note pages of each of these milestone/release but if for some reason you have some direct links (e.g. in a research paper, in a tutorial) you may have to update them.

Examples of URLs:

Best regards

Didier

-- 
Didier Vojtisek
SED Rennes - DiverSE Team - LogicA Team
Inria, Univ Rennes, CNRS, IRISA
Campus de beaulieu
35042 Rennes
02 99 84 75 07


-- 
Didier Vojtisek
SED Rennes - DiverSE Team - LogicA Team
Inria, Univ Rennes, CNRS, IRISA
Campus de beaulieu
35042 Rennes
02 99 84 75 07

-- 
Didier Vojtisek
SED Rennes - DiverSE Team - LogicA Team
Inria, Univ Rennes, CNRS, IRISA
Campus de beaulieu
35042 Rennes
02 99 84 75 07

Back to the top