Re: [Audacity-devel] Publishing releases

[Robert H. <aar...@gm...>]

Steve, what do you mean with release exactly?
Normally, it is just a zipped version of that tag.
You can add binary files directly on GitHub as artefacts, if you want that.

Apropos artefacts, AppVeyor does now delete them after three months.

Cheers
Robert

On 01/06/2018, Steve the Fiddle <ste...@gm...> wrote:
> According to GitHub, our latest release is Audacitry 2.1.3
> https://github.com/audacity/audacity/releases
>
> I "think" this is because James "Created a Release" for Audacity
> 2.1.3, but this has not been done for releases since that one.
> https://help.github.com/articles/creating-releases/
>
> It looks like the tag for 2.2.2 can be edited and a release created
> after the fact, which I think will update the "Latest Release" label.
>
> 1) Does anyone know for sure how this works?
> 2) Anyone confident enough to fix it?
> 3) Should this be part of the (documented) release process?
>
> Steve
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> audacity-devel mailing list
> aud...@li...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>