- Capture the version used to generated.
- Check at compile time and runtime that generated code isn't from a newer
  version, also check that the min version required is also supported.
- Keep the old constants/macros/functions to special case the last version
  that was working so those generated sources still work until we decide
  otherwise.

Add https://metacpan.org/pod/Google::ProtocolBuffers::Dynamic

benchmarks: update readme.txt

Compatibility with the new version of Bazel.

Allow the JsonFormat.Parser to ignore unknown fields

Fix Win32 error messages on Unicode build

Generalize plugin support in Bazel Skylark rule

include std::find()

Update repo in Bazel build files to use googletest instead of the deprecated gMock

Objc any helpers

Global variable HOST_CFG is deprecated and will not be supported soon.

Fix error and add note about lossy issues

Support the -Wassign-enum compiler flag.

The default behaviour of throwing an exception remains

- Capture the ObjC prefix used when generating the the file.
- Track the containing type on descriptors.
- Mark descriptors where the message class name got a suffix added to it.
- Expose a fullName property on Descriptors.
- Add helpers for packing/unpacking Any messages.
- Bump the ObjC runtime version number. Since we added methods and invoke them
  in the generated code, ensure the code is running against a matching version.
  Otherwise, someone could compile against headers, but run with a framework
  that is older and get unknown selector failures.  This should trip clearer
  messaging.

Fixes https://github.com/google/protobuf/issues/1674

Fix #2071 replacing /bin/sh with bash when generates descriptor

On Ubuntu /bin/sh is dash by default, this can cause
generate_descriptor_proto.sh fail to execute.

Fix to typo/oversight in reflection tests

This check adds a few constraints on the way to build a project when we have
a proto file which imports another one. In particular, on projects which
build both C# and Java, it's easy to end up with exceptions like

    Expected: included.proto but was src/main/protobuf/included.proto

A user may work around this issue, but it may add unnecessary constraints
on the layout of the project.

According to https://github.com/google/protobuf/commit/f3504cf3b1d456a843e8242fdee9ba0bf2991dc1#diff-ecb0b909ed572381a1c8d1994f09a948R309
it has already been considered to get rid of this check, for
similar considerations, and because it doesn't exist in the Java code

Fix #1955 clang-tidy warning misc-macro-parentheses

clang-tidy gives warning "macro argument should be enclosed in
parentheses" to macro ZR_, the "first" parameter.

fix #1342 cause by ownership issues

Make Root's +extensionRegistry generation smarter.

Fix to typo/oversight in python tests, only affecting python 3

At generation time, walk the file's dependencies to see what really contains
extensions so we can generate more minimal code that only links together the
roots that provided extensions. Gets a bunch of otherwise noop code out of
the call flow when the roots are +initialized.

Remove unused vector

Restore New*Callback into google::protobuf namespace …

update the OSGi metadata for the javanano package