Ruby: generated foo.proto -> foo_pb.rb instead of foo.rb.

This brings us more into line with other langauges, and makes it more
obvious when we are requiring protobuf generated code.

Fix maven links.

Correctly sets the generate_for_named_framework option after parsing.

Ruby: encode and freeze strings when the are assigned or decoded.

Change-Id: I252d7a644a9e4064a9f1a816a2be3f25f37b4c43

 - Also updates the documentation with a bit more information.

Remove linux tests from travis.

Fix sign-comparison warnings and add a test for that.

[ci skip]

Change-Id: Ibefbdf441d932c5751235c635244450d7cbacc53

When it runs in parallel with other jenkins tests, multiple tests start
to fail probably because cpp_distcheck will update the C++ lib that
other tests (such as python_cpp) are depending on.

Change-Id: Ibca0243084bb6b81c811b62c75288e20cc2aabf5

These tests are already covered by jenkins and right now jenkins can
finish these tests much quicker then travis.

Change-Id: I5799761ccc338211d750940e3cf4c8e2569c8144

grpc build treates them as errors and such issues (protobuf change
breaks grpc) has been reported repeatedly. For example:
  https://github.com/google/protobuf/issues/1813

Change-Id: I077c4557cf3effd5195f88802c38999b884edc30

Add more tests to jenkins.

Fixes the parsing of the proto-framework map file.

 - Fixes memory issue where the pointer to the StringPiece would be allocated on the stack, and would mangle the output.
 - Fixes length of the file name when parsing the comma separated files.

1. Added ruby22 and jruby tests to jenkins.
2. Added javascript tests to jenkins.
3. Added golang tests to jenkins.
4. Removed ruby19/ruby20 tests from travis. Support for ruby 2.0 has
   ended since 2016/02/24.
   https://www.ruby-lang.org/en/news/2016/02/24/support-plan-of-ruby-2-0-0-and-2-1/

Change-Id: Ie984b06772335352a4be7067ab2485f923875685

Update travis tests for Java.

1. Set JAVA_HOME so mvn can pick up the correct java version.
2. Remove jdk6 tests. It has been broken for a while and remain undetected as
   mvn is actually using java 7 to build the code. Given that we have
   set -source and -target to 6 in the pom.xml and the built .jar
   should be usable by java 6, having a dedicated java 6 test doesn't
   seem necessary (assuming very few Java 6 users want to compile protobuf
   Java from source).

Change-Id: I4f14da772632df3e47801f180198242b306c3f0f

Add missing files in EXTRA_DIST and add a test.

Change-Id: If80725402173cdf50969cb08e7fe5affe3532fb2

Versioning Java GeneratedMessage class

Use the dotnet-release package feed for Travis.

JavaScript: Make implicit defaults consistent with explicit defaults

See https://github.com/dotnet/core/issues/227 for background.

Change-Id: I56a6cce613462794f172ff2e62b25d8a9fc162f3

Change-Id: I991396ac6e51e32f3ab1daa501d625f34c3ecb04

Change-Id: Ib2bb5042deaabdf452d5be2ad1ce40d739ad8d1b

JavaScript: segregate references to binary functionality