Re: Github Releases, with excellent timing

[Anil Madhavapeddy <anil@xxxxxxxxxx>]

On 3 Jul 2013, at 14:08, Daniel Bünzli <daniel.buenzli@xxxxxxxxxxxx> wrote:

> Le mercredi, 3 juillet 2013 à 11:31, Anil Madhavapeddy a écrit :
>> Github just announced their new Release workflow, which looks excellent.
>> https://github.com/blog/1547-release-your-software
> 
> 
> It may work for you but that doesn't look different from the ability that was 
> already existing to be able to download the checkout associated to a tag. 
> They just renamed the "tags" tab in "releases" (which is completely stupid 
> from a git semantics point of view, a tag is not necessarily a release) and 
> added a way to attach text and files to a tag.
> 
> For me, as long as you cannot perform arbitrary transformation on the tree 
> checkout to transform it into the released tree, this is going to be useless. 
> I actually hate the fact that this cannot be disabled if you try to download 
> what they now call a "release" for this specific package:

It looks like you can attach arbitrary files to the release -- which have the 
transforms (setup.ml, utf files, etc).  Isn't that enough?

See:
> You can also attach binary assets (such as compiled executables, minified 
> scripts, documentation) to a release. Once published, the release details and 
> assets are available to anyone that can view the repository.

So you just need to mark the source asset differently from the tagged pristine 
source tarball.

-anil