Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Soft Works <softworkz@hotmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] FFmpeg 5.0 LTS vs 5.1 LTS
Date: Mon, 25 Apr 2022 19:40:38 +0000
Message-ID: <DM8P223MB03659B82FFEC1067EF6172A2BAF89@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20220425184006.GZ2829255@pb2>



> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> Michael Niedermayer
> Sent: Monday, April 25, 2022 8:40 PM
> To: FFmpeg development discussions and patches <ffmpeg-
> devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] FFmpeg 5.0 LTS vs 5.1 LTS
> 
> On Mon, Apr 25, 2022 at 08:04:25PM +0200, Jean-Baptiste Kempf wrote:
> > On Mon, 25 Apr 2022, at 19:19, Michael Niedermayer wrote:
> > > On Mon, Apr 25, 2022 at 01:51:26PM +0200, Jean-Baptiste Kempf
> wrote:
> > >> On Sat, 23 Apr 2022, at 18:36, Michael Niedermayer wrote:
> > >> > Do people prefer that 5.0 becomes LTS or the next (5.1) ?
> > >> > Or something else ?
> > >>
> > >> My understanding of the consensus was;
> > >> - 5.0 in Dec/Jan
> > >> - 5.1 in Jul with API additions, but no ABI/behavior breakage
> > >
> > > yes
> >
> > OK.
> >
> > >> - 6.0 in Dec 22 with ABI/API/behavior breakage and while 5.1
> becomes LTS
> > >
> > > we could give 5.1 an LTS "tag" when its released already
> >
> > I would mention it, tbh.
> >
> > > also thers the possibility that by december we have nothing that
> really
> > > benefits from a ABI/API/behavior breakage.
> > > If that happens people might prefer 5.2 over 6.0 i dont know.
> >
> > I think it would be clearer to accustom people that we have one big
> potential change every year, at the same date.
> 
> thats not a bad idea. Still bumping the sonames of the libs when there
> is
> no reason is not really nice. I dont know if we will have a reason in
> december

I think, the most valid reason to increase a version number is the
publishing of a release :-)


Totally crazy concept:


ffmpeg 6.0

  libavutil.so.6.0.100
  libavcodec.so.6.0.100
  libavfilter.so.6.0.100
  libavformat.so.6.0.100
  ...

ffmpeg 6.1

  libavutil.so.6.1.100
  libavcodec.so.6.1.100
  libavfilter.so.6.1.100
  libavformat.so.6.1.100
  ...

Best,
softworkz

(yes, I mean no cross-version compatibility)
_______________________________________________
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-04-25 19:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-23 16:36 Michael Niedermayer
2022-04-23 16:40 ` James Almer
2022-04-23 18:08   ` Neal Gompa
2022-04-23 18:14     ` James Almer
2022-04-23 18:17       ` Neal Gompa
2022-04-24  9:18 ` Gyan Doshi
2022-04-24  9:55 ` Steven Liu
2022-04-24 22:48 ` Soft Works
2022-04-25  8:01   ` Paul B Mahol
2022-04-25  9:04     ` Soft Works
2022-04-25 11:51 ` Jean-Baptiste Kempf
2022-04-25 17:19   ` Michael Niedermayer
2022-04-25 18:04     ` Jean-Baptiste Kempf
2022-04-25 18:40       ` Michael Niedermayer
2022-04-25 19:40         ` Soft Works [this message]
2022-04-25 19:44         ` Jean-Baptiste Kempf
2022-04-26 13:32           ` Michael Niedermayer
2022-04-25 18:38     ` James Almer

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=DM8P223MB03659B82FFEC1067EF6172A2BAF89@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
    --to=softworkz@hotmail.com \
    --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