ANGLE versions for external projects

[anatoly techtonik]

Hi.

How to download stable ANGLE versions? And how to track

changes among releases? Is there such thing as ANGLE

releases, or everybody just downloads the master tgz from

repository browser?

https://chromium.googlesource.com/angle/angle

[Jamie Madill]

We don't do releases. If I were you I'd just pick the current master and if you have to freeze it, don't update.

If you want you can also look at the chromium version branches. You can cross-reference current Chromium stable/beta/dev from omaha proxy and pick the chromium/#### branch that corresponds with those.

--
You received this message because you are subscribed to the Google Groups "angleproject" group.
To unsubscribe from this group and stop receiving emails from it, send an email to angleproject...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Geoff Lang]

A follow up on how to pick the versions of ANGLE that Chrome uses:

Take a look at http://omahaproxy.appspot.com/ and notice how the current Chrome stable version on Windows is 49.0.2623.87.  This means that the current stable Chrome version is using the chromium/2623 branch of ANGLE.

--

[anatoly techtonik]

Is master always stable? Or it is better to fetch ANGLE from stable/beta/dev?

[Shannon Woods]

Master is stable-ish-- at most points, it's stable enough to be used in Chrome Canary. The downside of master is that it updates frequently, and if you're only interested in knowing when there's a critical stability or security update, it's hard to separate those on master from the routine development work. Choosing a branch used by stable or beta ensures that, if we need to make a significant fix that affects that branch during the lifetime of the release, it'll appear on the branch, and you can take the update without also taking all the other changes that have gone in to master.

That said, Chrome releases have a limited lifespan-- the usual time from when a branch becomes Beta to when it is retired as an outgoing Stable release is 12 weeks. So choosing a branch used for a stable or beta release will only get you a short window of updates in any case. 

(There's more detail on choosing a branch here: https://chromium.googlesource.com/angle/angle/+/master/doc/ChoosingANGLEBranch.md )

[anatoly techtonik]

> https://chromium.googlesource.com/angle/angle/+/master/doc/ChoosingANGLEBranch.md

Nice that there is a documentation for that. The only missing info is
how to update ANGLE version in
https://chromium.googlesource.com/angle/angle/+/master/src/commit.h
so that it is clear for humans what was the original branch point for
copying code.

Looks like this should be done manually, because the script
https://chromium.googlesource.com/angle/angle/+/chromium/2689/src/commit_id.py
only works if I clone the code and choose the branch. And it just
records the hash of the commit, not the branch version.

[anatoly techtonik]

I am still thinking about this commit_id.py

https://chromium-review.googlesource.com/#/c/349040/

It would be more useful if it could automatically fetch current stable Chrome version and update working copy to that. Also produce commit.h labelled that it contains stable Chromium version.

BTW, original commit.h contains #define ANGLE_DISABLE_PROGRAM_BINARY_LOAD which is erased when commit.h is regenerated. Is it intentional?

[Jamie Madill]

On Fri, Jun 3, 2016 at 2:40 AM, anatoly techtonik <tech...@gmail.com> wrote:

I am still thinking about this commit_id.py

https://chromium-review.googlesource.com/#/c/349040/

It would be more useful if it could automatically fetch current stable Chrome version and update working copy to that. Also produce commit.h labelled that it contains stable Chromium version.

I'm not sure it would be that helpful. It's really meant to be something that's generated at compile time, when you are building from Git, and irrespective of Chromium.

 

BTW, original commit.h contains #define ANGLE_DISABLE_PROGRAM_BINARY_LOAD which is erased when commit.h is regenerated. Is it intentional?

Yes, the "original" commit.h is a dummy file for use when there is no git repository. In that case ANGLE doesn't know what version it is, and can't use program binaries since they're dependent on versioning.