Status Update
Comments
ma...@gmail.com <ma...@gmail.com> #2
I created one ticket per library to be updated since Edwin told me to do so.
Should we amend the procedure I documented based on Edwin's input in
gh...@google.com <gh...@google.com> #3
I've made a summary of these requests and concluded that we can upgrade some of the libraries because the version we intend to upgrade to match our internal version.
I'll update child tickets separately.
st...@gmail.com <st...@gmail.com> #4
ha...@gmail.com <ha...@gmail.com> #5
ek...@google.com <ek...@google.com> #6
xe...@gmail.com <xe...@gmail.com> #7
po...@google.com <po...@google.com> #8
We didn't come up with a very clear process.
We discussed having a documentation page that lists which versions of libraries are supported and then support newer versions of the library in upstream as long as the usage of said libraries conforms (API wise) to the versions that are stated as supported. This is non-ideal.
Another thing we discussed was fast-tracking library upgrades for security purposes.
Description
Creating a single ticket for library upgrades to make it easier for us to manage them in a single place.
Docs:https://gerrit-review.googlesource.com/Documentation/dev-processes.html#upgrading-libraries