search

ericmckean / webm

Automatically exported from code.google.com/p/webm
0 stars 0 forks source link

Release 1.3 #648

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
-Create a 1.3 branch.
-Tag 1.3
-Release 1.3 snapshot

Original issue reported on code.google.com by fgalli...@google.com on 17 Oct 2013 at 9:34

GoogleCodeExporter commented 9 years ago 
"forest" branch created.

Original comment by johannko...@google.com on 17 Oct 2013 at 9:51

GoogleCodeExporter commented 9 years ago

Original comment by fgalli...@google.com on 17 Oct 2013 at 10:25

GoogleCodeExporter commented 9 years ago

Original comment by ya...@google.com on 17 Oct 2013 at 10:54

GoogleCodeExporter commented 9 years ago 
Ignore the new branch for now. We'll branch after the CHANGELOG has been merged.

Original comment by johannko...@google.com on 17 Oct 2013 at 11:09

GoogleCodeExporter commented 9 years ago

Original comment by ya...@google.com on 18 Oct 2013 at 1:08

GoogleCodeExporter commented 9 years ago 
Where is 1.3.0 tarball now that it is tagged in git?

Original comment by marcos...@gmail.com on 4 Dec 2013 at 12:17

GoogleCodeExporter commented 9 years ago 
Packagers are waiting on 1.3.0 tarball

Original comment by ArcRi...@gmail.com on 10 Dec 2013 at 2:56

GoogleCodeExporter commented 9 years ago 
I have 4 blocking issues to investigate and decide if they should be backported:
https://gerrit.chromium.org/gerrit/#/c/68012/
https://gerrit.chromium.org/gerrit/#/c/67979/
https://gerrit.chromium.org/gerrit/#/c/68005/

The 4th is vp9 fuzz testing with:
zzuf -M -1 -q -s 586 -r 0.001:1 < ~/vp90-2-00-quantizer-31.webm > crash.webm

Original comment by johannko...@google.com on 10 Dec 2013 at 5:38

GoogleCodeExporter commented 9 years ago 
Shouldn't the 1.3 tag be removed if its not ready for release?

Original comment by ArcRi...@gmail.com on 10 Dec 2013 at 7:38

GoogleCodeExporter commented 9 years ago 
Unfortunately tags can't be revised. If the changes warrant an update, it will 
be 1.3.1

Original comment by johannko...@google.com on 10 Dec 2013 at 11:43

GoogleCodeExporter commented 9 years ago 
So long as the public API isn't going to change, and considering this tag will 
remain what is considered 1.3.0, can we get a 1.3.0 tarball up so 3rd party 
packages can start adding VP9 support?

Packaging against a tarball is much easier than a git revision.  We can always 
push an update when 1.3.1 is released.

Original comment by ArcRi...@gmail.com on 11 Dec 2013 at 12:04

GoogleCodeExporter commented 9 years ago 
Okay, it's been over a month.

Original comment by alex.hel...@gmail.com on 6 Jan 2014 at 1:45

GoogleCodeExporter commented 9 years ago 
Many Linux distributions have package version freezes for their upcoming 
releases coming up in the next few weeks (Fedora, Ubuntu).

In other words, if 1.3.x isn't released in tarball/zip form soon we won't have 
VP9 support for a vast majority of Linux users for another 10 months.

Original comment by ArcRi...@gmail.com on 6 Jan 2014 at 2:23

GoogleCodeExporter commented 9 years ago 
libvpx 1.3.0 snapshot tarballs are posted here: 
https://code.google.com/p/webm/downloads/list

Original comment by louquil...@google.com on 10 Jan 2014 at 11:16

GoogleCodeExporter commented 9 years ago 
If you have any issues with the release please follow up on the mailing list or 
the 1.3.1 bug:

https://code.google.com/p/webm/issues/detail?id=691

Original comment by johannko...@google.com on 10 Jan 2014 at 11:53