Triage issues for v0.4.0
There has been a ton of work done since v0.3.3. We should cut out a new release.
However, I get the feeling that there are some regressions with it. We should triage the tickets still open since v0.3.3 to make sure they can be "ignored" for a new release.
(edited to just be the issues left to address)
-
Assert no blocking issues on GitHub: -
Document everything backwards incompatible in changelog: -
Stream.encodereturns a list of packets, instead of a single packet. -
AudioFifoandAudioResamplerwill raiseValueErrorif input frames inconsistantpts. -
CodecContext.ratehas been removed, but proxied toVideoCodecContext.framerateandAudioCodecContext.sample_rate. The definition is effectively inverted from the old one (i.e. for 24fps it used to be1/24and is now24/1). -
Fractions (e.g. time_base,rate) will beNoneif they are invalid. -
InputContainer.seekandStream.seekwill raise TypeError if given a float, when previously they converted it from seconds.
-