[MEI-L] Google Code deprecating downloads

[Roland, Perry (pdr4h)]

We're already providing downloads from music-encoding.org.

For individual files, links point a location inside a tag, e.g., http://music-encoding.googlecode.com/svn/tags/MEI2013_v2.1.0/schemata/mei-CMN.rng, but for a "package" of files, links point to files in the download area, e.g., http://music-encoding.googlecode.com/files/MEI2013_v2.1.0.zip.

It's the last kind that's going to become problematic.  Putting the ZIP file inside the repo and then making it part of a tag makes it accessible.  Maintaining the links at music-encoding should be manage-able.

--
p.

__________________________
Perry Roland
Music Library
University of Virginia
P. O. Box 400175
Charlottesville, VA 22904
434-982-2702 (w)
pdr4h (at) virginia (dot) edu
________________________________________
From: mei-l [mei-l-bounces at lists.uni-paderborn.de] on behalf of Peter Stadler [stadler at edirom.de]
Sent: Tuesday, November 19, 2013 11:38 AM
To: Music Encoding Initiative
Subject: Re: [MEI-L] Google Code deprecating downloads

Am 19.11.2013 um 16:22 schrieb Raffaele Viglianti <raffaeleviglianti at gmail.com>:

> What Andrew said. Also, using GitHub "releases" could give us a consistent way of tracking and distributing MEI releases. Were GitHub to disappear, their releases are nothing more than Git tags, so they could be migrated without too much hassle.
Yes and no. When creating a git tag (and pushing it to GitHub) it shows up as a GitHub release. But, you can add additional binaries and a change log that goes „beyond Git artifacts“ [1]. Just wanted to mention though I still prefer that option …

This GoogleCodeWiki hack seems a little bit too hacky to me but we could simply provide downloads directly from music-encoding.org as well. There are currently four files in the downloads section from GoogleCode — that should be manageable?! As I understand the "Change to Google Code Download Service“ it only affects this downloads section, not the repository.

Best
Peter


[1] https://github.com/blog/1547-release-your-software