[FFmpeg-devel] 0.7 / 0.8 Releases
stefano.sabatini-lala at poste.it
Wed Jun 22 18:21:33 CEST 2011
On date Wednesday 2011-06-22 16:37:35 +0200, Michael Niedermayer encoded:
> On Wed, Jun 22, 2011 at 04:05:23PM +0200, Stefano Sabatini wrote:
> > On date Wednesday 2011-06-22 15:39:08 +0200, Michael Niedermayer encoded:
> > > On Wed, Jun 22, 2011 at 08:10:40AM +0100, Gavin Kinsey wrote:
> > > > On Tuesday 21 June 2011 22:19:34 Michael Niedermayer wrote:
> > > > > Hi
> > > > >
> > > > > the 0.7 / 0.8 Releases are up
> > > > > please check them
> > > >
> > > > Is there a branch or tag in git for the releases?
> > >
> > > as libav uses vX.Y tags i picked n0.8 for us for the ffmpeg 0.8
> > > release.
> > >
> > > 0.7 will get n0.7 when its officially released
> > >
> > > branches will be created when needed
> > $ git branch -r
> > origin/HEAD -> origin/master
> > origin/master
> > origin/oldabi
> > origin/release/0.5
> > origin/release/0.6
> > In order to avoid confusion I propose to rename origin/oldabi to
> renaming public branches would break clones
Then please create a separate 0.7 branch, and deprecate the oldabi
branch, the "oldabi" name is pointless in this scheme.
> > origin/release/0.7, and create a separate origin/release/0.8 for the
> > 0.8 release. I don't know if it is a good idea to use tags, since that
> > should be rather considered a *branch*.
> each 0.7 release (0.7 0.7.1 0.7.2 ...) should get a tag on the 0.7
> but until we want to do some work toward a 0.7.1 or 0.8.1 theres no
> need for the branch
> > And BTW, having a branch named "Peace and Love" and one just "Love" is
> > confusing, you could call one of them "Peace" and the second "Love"
> > and call them collectively as "Peace and Love", or give an entirely
> > different name to the second.
> RELEASE_NOTES: say this:
> * 0.8 "Love" June, 2011
> * 0.7 "Peace" June, 2011 (identical to 0.8 but using 0.6 ABI/API)
FFmpeg 0.8 "Love"
FFmpeg 0.7-rc1 "Love and Peace"
FFmpeg = Fanciful Fancy Murdering Philosofic Exciting Game
More information about the ffmpeg-devel