Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] GitHub releases section is very old
Date: Sat, 29 Oct 2022 14:53:34 +0200
Message-ID: <ce2614e2-ffbb-b840-7bea-800c00357de1@rothenpieler.org> (raw)
In-Reply-To: <PA4PR01MB99224BF4CE573E8076EECD7BCB359@PA4PR01MB9922.eurprd01.prod.exchangelabs.com>

On 29.10.2022 14:36, * Neustradamus * wrote:
> Hello all,
> 
> It is possible to remove all releases from GitHub?
> Because at right, we can see and it is not good promotion for this active project:
> - https://github.com/FFmpeg/FFmpeg
> 
> Releases 11
> FFmpeg 3.0 Release
> Latest on 15 Feb 2016
> + 10 releases
> - https://github.com/FFmpeg/FFmpeg/releases
> 
> The important part is here:
> - https://github.com/FFmpeg/FFmpeg/tags
> 
> But it is possible to add all time in releases section, a new release with changelog...

We should probably delete all existing releases instead, so they don't 
cause confusion like this.
Github is just a mirror, not any kind of official release channel.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

  reply	other threads:[~2022-10-29 12:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-29 12:36 * Neustradamus *
2022-10-29 12:53 ` Timo Rothenpieler [this message]
2022-10-29 19:31   ` Michael Niedermayer
2022-11-26 21:14     ` Michael Niedermayer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ce2614e2-ffbb-b840-7bea-800c00357de1@rothenpieler.org \
    --to=timo@rothenpieler.org \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git